bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "cvs move" command


From: Pierre Asselin
Subject: Re: "cvs move" command
Date: Wed, 8 Jan 2003 19:25:21 +0000 (UTC)
User-agent: nn/6.6.4

In <address@hidden> Stewart Heitmann <address@hidden> writes:

>I would love the CVS development team
>to develop a "cvs move" command to
>replace the clunky "cvs remove" + "cvs add".

>[ ... ]

>I suggest a "cvs move [srcfile] [destfile]"
>command that copies the repository srcfile,v
>file to destfile,v in the repository (thus
>the new file retains its revision history).
>Then it does a cvs remove on the original
>srcfile so it can be reinstated later if needed.

It also needs to remove all tags from destfile,v .  Except if this
is happening on a branch, in which case destfile,v should still
have the tag for that one branch.  Does the copy happen immediately,
or is it just scheduled to happen on the next commit, like add and
remove? Is there an extension to the client-server protocol?  Is
the new protocol backward-compatible?  Do new clients interoperate
cleanly with old servers?


>Its very simple and I cant think of any reason
>it wouldnt work.

It's very simple except when you look at the details.  If my list
above is complete it may indeed not be too bad, but did I leave
anything out?

I'm such a grouch.  On a more constructive note, maybe meta-cvs can do
the job.  I haven't tried it yet, but that's the kind of limitation it
tries to address.  Kaz gives these url's:

    http://freshmeat.net/projects/mcvs
    http://users.footprints.net/~kaz/mcvs.html



reply via email to

[Prev in Thread] Current Thread [Next in Thread]