[Adium-devl] VCS + SVN 1.5

[Chris Forsythe]

On Dec 26, 2007, at 9:36 AM, John Bailey wrote:

> Colin Barrett wrote:
>> On Dec 25, 2007, at 9:39 PM, Augie Fackler wrote:
>>> Mercurial: Serving could be hard. Large on-disk history if we  
>>> bring in
>>> the entire history.
>>
>> Aren't this issues with the other ones as well?
>>
>> -Colin
>
> I'm a relative outsider here, being one of the most recent group to  
> be named a
> Pidgin developer, and I barely use Adium, but I have a couple  
> thoughts that are
> probably relevant here:
>
> To varying degrees, yes history does become somewhat large.  For  
> example,
> Pidgin's monotone has 23,600 revisions on the central database.   
> The database is
> approximately 237MB.  Considering that we imported our *entire*  
> history into
> monotone, I think this is quite reasonable.
>
> I remember one of our developers experimented with git once when we  
> were still
> using CVS, and at the time the complaint seen most frequently was  
> that the
> history was over 600MB at the time.
>
> 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