[EMAIL PROTECTED] on 03/06/2000 11:06:11 PM
>I like the windows find tool that combines find, xargs, and grep in
>one box. Yes, it's limited, but it often works faster than trying to
>get the correct command typed in. And, it's more of what I think of.
Oh no, declaration of religious war ;) CVS was born out of Unix, it'll stay
that way. If you want higher level tools, nothing is stopping anyone from
building them (don't compilers still call the assembler to create object files?
aren't automatics just a layer on top of sticks (ie manuals)?).
>I don't want to be told "Here's a list of commands you can use to get
>this done". I want one command that does it.
>
>I don't want to have to remember a list of steps, and worry about "did
>I make a mistake anywhere?".
You can create scripts to achieve this.
>Yes, there is the ability to do this in CVS. As you said,
>> Cripes, use "cvs diff" to give you a diff of your changes, checkout
>> a new sandbox (or revert your old one), add the branch, apply the
>> diffs (using patch), commit.
>So I need to use diff, a temp file, a new checkout, and patch. Why not
>have it all in one command?
You can, through a script. In fact, I don't think you even need a temp file.
>Right now, I can (usually, not always, and no I don't remember why it
>failed when it did) do:
>To decide that I want to create a branch at checkin, with modified
>files:
>cvs tag base-branch
>cvs tag -b branch
>cvs update -r branch
>cvs commit
>
>Why do I need 4 commands to do one operation?
'cos if everyone got all the conglomerate commands they wanted, CVS would be
bloated and unwieldy while not providing any more functionality it already had.
>Just now I made some changes to files, and realized that what I had
>should have been merged onto the trunk before I made these changes.
>Nothing else had been modified on the trunk since my branching. So, in
>theory, I could say
>
>cvs move-branch removeLocks onto-parent as-branch base-newrevision //
>THIS DOESN'T EXIST -- modify repository only
>cvs rtag -r base-newrevision -b newrevision // modify repository --
>make new branch
>cvs update -r newrevision // switch my newly modified files onto
>newrevsion
>cvs commit
>
>That's another 4 commands, one of which doesn't exist, unless I do a
>lot of diff, revert, patch, etc.
>
>Why?
'cos you made a mistake to begin with.
>Why not put all that into CVS? The "flying fish" approach to the
>repository is really the (my opinion) proper way to use it. Otherwise,
>you can only commit a change when it is ready for prime time, or else
>you will hose every other developer.
If you get into the habit of creating and working on task branches, this
wouldn't happen.
Noel
