Subject: Re: kernel filesystem code move
To: Luke Mewburn <firstname.lastname@example.org>
From: Andrew Brown <email@example.com>
Date: 12/29/2002 15:25:30
>I've been bitten in the past trawling through the cvs revision history
>where the revisions had been marked dead (which you need to do if repo
>copying, otherwise date based checkouts fail), and finding that all I
>could see was the log messages; cvs diff and cvsweb were useless as
>far as finding out the "guts" of the change.
people say that "repository copy" should be used so that "history is
not lost", yet with the requirement of repository copy being that all
"previous revisions" be marked dead (so that date based checkouts
"work", ie when you check out the source for a given date, you don't
get this new file that didn't really exist at that time), the history
is still lost. all that is preserved is the log entry, which might be
interesting, but isn't terribly helpful.
what if instead of being marked dead, all the "previous revisions" had
their date changed to the current time. date based checkouts would
still work...diffs with previous revisions would still work...
hmm...revision based checkouts will still pull out files there weren't
any more ideas?
|-----< "CODE WARRIOR" >-----|
firstname.lastname@example.org * "ah! i see you have the internet
email@example.com (Andrew Brown) that goes *ping*!"
firstname.lastname@example.org * "information is power -- share the wealth."