: I will do what you ask for, Hoss, although the cloned git repo records
: every single SVN revision in the commit log anyway, so it should be
: relatively easy to find which commit (SVN and otherwise) preceded the
: move.

Sure -- my suggestion was not based on any worries about the "post svn" 
world ... my suggestion was purely based on concerns for:

a) people who forget/don't-know that the migration is happening and do an 
"svn update" this weekend and then want to be able to get back to the 
last useful r# they can develop/test against while they wait for the git 
repo to be available

a) people who might only casually follow lucene/solr dev who do an "svn 
update" a few weeks/months from now and then wonder where the fuck all the 
files went; and/or may not really care enough about long term development 
to bother cloning the git repo -- but still want to get their local svn 
copy back to the state it was before the migration.

..at least having that info in the last svn log message for the directory 
will be a little help (although adding a README_MOVED_TO_GIT.txt file with 
the same info after the 'purge all files comment' would probably also be a 
good idea so people don't even have to check the svn log.)


-Hoss
http://www.lucidworks.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to