Adam R. B. Jack wrote:
(2) hoping to clean out/re-organize now (prior to any such 1 above).
As long as we keep the history of "traditional" in CVS I don't care too much whether it gets migrated to SVN at all. It's not as if we'd remove the CVS module completely, it will just become unused.
I think this is a key point, especially since the cvs2svn run is likely the big bottleneck w/ [EMAIL PROTECTED] I'd like to get one last clarification before I write to infr@ (and copy [EMAIL PROTECTED]).
1) We ask for a gump tree in SVN [letting them know we'll keep the gump module in CVS.] 2) We mark tag gump CVS as 'TRADITIONAL'. 3) We remove all the older/unused (traditional) contents, and we move all Python code to SVN, leaving only the metadata directories. 4) We commit Python to SVN.
Good enough for folks?
No, please, do this instead:
1) [fine] 2) use cvs2svn to migrate gump CVS over gump SVN 3) tag gump CVS as "PRE_SVN_MIGRATION" 4) remove everything from gump CVS that is not metadata 5) cleanup the gump SVN repository as you wish
All right, I volunteer to help with 2).
-- Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
