[drupal-devel] Retaining CVS history over moves (was:
gordon at heydon.com.au
Thu May 5 03:36:36 UTC 2005
If you read the cvs manual you will see that you actually have to manually
move files in the archive itself. The is done outside of the cvs interface.
So it is a real pain.
From: drupal-devel-bounces at drupal.org
[mailto:drupal-devel-bounces at drupal.org] On Behalf Of Tom Dobes
Sent: Thursday, 5 May 2005 1:29 PM
To: drupal-devel at drupal.org; chris at tinpixel.com
Subject: [drupal-devel] Retaining CVS history over moves (was:
On 5/4/05, Chris Johnson <chris at tinpixel.com> wrote:
> Gordon Heydon wrote:
> > <cvs rant>
> > Moving the bluemarine PHPTemplate theme into core is one of the main
> > that I am starting to dislike cvs. Because of the move all the history
> > this is gone, and even the more importantly the credit to me. Also the
> > accountability that this is 100% GPL code is also lost as there is no
> > history before the initial commit.
> Umm, well, that's a function of how the move was done, not just CVS --
> although I admit CVS doesn't make it as easy as one would like. But
> bluemarine could have been moved with all history intact.
Really? How? Could you point me / us to some docs or write a quick
how-to? This has come up a couple of times, even just within the
contrib repository when stuff was being rearranged. I've read the CVS
docs (quite a while ago), but I don't remember seeing anything about
this type of ability.
More information about the drupal-devel