[Adium-devl] VCS + SVN 1.5

[John Bailey]

Chris Forsythe wrote:
>> Another thing to consider is that there will almost certainly be  
>> issues
>> importing your entire svn history into another VCS--it is very easy  
>> to create
>> history that conversion tools will choke hard on.  The classic  
>> example is if
>> there were any files renamed/moved *and modified* in the same  
>> revision in svn.
>> When we converted from svn to monotone, there were a number of  
>> revisions in
>> which Ethan, our monotone expert, had to recreate the revision by  
>> hand.  Good
>> examples of this are the six svn revisions that comprised the tree  
>> restructure
>> between our 2.0.0beta3 and 2.0.0beta4 releases.  There are other  
>> examples of
>> both "bad" history in svn and cases in svn history which will cause  
>> conversion
>> tools to give up and stop processing.
> 
> Do you happen to know which six revisions these were?
> 
> Chris

In monotone, Ethan committed the revision by hand as
061603b195f389b5ea40d5dcaa73ba878be8af3d (note that generally only the first 8
digits of a revision number are necessary for identification), but that single
mtn revision comprised our old svn revisions of 16854 through 16861.  The actual
trouble revisions are 16855 through 16859--the additional revisions were
necessary to create points from which tailor could clearly understand the state
of both repositories.

The svn revisions are still available through Sourceforge's ViewVC.
http://pidgin.svn.sourceforge.net/viewvc/pidgin?view=rev&revision=16855 is the
first trouble revision.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20071226/38f959d0/attachment.sig>