I saw quite a few updates this morning in cvs as well.
> Should we declare a code freeze at some point?
Could you email everyone who made a commit to CVS and let them know
that those changes need to go into the svn repository instead, with
all due apologies. I'm not sure what you mean about a code freeze.
It would have been smart to tag CVS before the migration so that we
could run a diff against the tagged version and then just apply the
diff to svn. Oh well, I'll have to remember that for next time.
JDH
I meant no more commits to cvs, but I sent that before I saw the "CVS
is dead" comment. So please just ignore me! 
···
On 2/28/06, John Hunter <jdhunter@...5...> wrote:
> I saw quite a few updates this morning in cvs as well.
> Should we declare a code freeze at some point?
Could you email everyone who made a commit to CVS and let them know
that those changes need to go into the svn repository instead, with
all due apologies. I'm not sure what you mean about a code freeze.
It would have been smart to tag CVS before the migration so that we
could run a diff against the tagged version and then just apply the
diff to svn. Oh well, I'll have to remember that for next time.
JDH
John Hunter a �crit :
It would have been smart to tag CVS before the migration so that we
could run a diff against the tagged version and then just apply the
diff to svn. Oh well, I'll have to remember that for next time.
You can still make a cvs diff between two dates if you know when the switch to the SVN occured.
···
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@...12... | aurelien@...327...
`- people.debian.org/~aurel32 | www.aurel32.net