[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Maintaining branches...
From: |
Paul Sander |
Subject: |
Re: Maintaining branches... |
Date: |
Thu, 14 Jun 2001 15:53:43 -0700 |
Sounds like two more command line options are in order: One to set the
default behavior in the .cvsrc file, the other to override that setting on
the command line.
--- Forwarded mail from address@hidden
On Wed, Jun 13, 2001 at 11:12:16PM -0700, Paul Sander wrote:
> Is there some reason why the -j's could not be recorded in the CVS directory,
> and corrected with each update? The joins shouldn't be recorded in the
> repository until the commits are done anyway.
>
> -j makes a notation in the CVS directory (or appends an existing one if
> multiple joins are done between commits), and -r and -A clear out the
> notations. At commit time, the notations could be recorded in the RCS
> files for future use.
When a file is in this merged-but-not-committed state, "rm foo;
cvs up foo" should do one of two things:
- erase the "-j" notation, or
- redo the merge(s)
Redoing the merge would basically make "-j" sticky -- but only a
little sticky, like a PostIt Note :-) -- since it should become
"unstuck" after a commit.
The former would preserve consistency with current behaviour; the
latter would bring this case more into line with the rest of CVS.
Which of these would be preferable?
--- End of forwarded message from address@hidden
- Maintaining branches..., Ralph Mack, 2001/06/12
- RE: Maintaining branches..., Stephen Cameron, 2001/06/12
- Re: Maintaining branches..., Ralph Mack, 2001/06/13
- Re: Maintaining branches..., Mike Castle, 2001/06/14
- Re: Maintaining branches..., Derek R. Price, 2001/06/14
- Re: Maintaining branches..., Mike Castle, 2001/06/14
- Re: Maintaining branches..., Derek R. Price, 2001/06/14
- Re: Maintaining branches..., Mike Castle, 2001/06/14
- Off list comment (was: Re: Maintaining branches...), Mike Castle, 2001/06/18
- Re: Maintaining branches..., Paul Sander, 2001/06/14