[ODE] From unstable to trunk...

Alen Ladavac alenl-ml at croteam.com
Thu Jun 30 15:29:15 MST 2005


Isn't Subversion supposed to have problems with branching? (i.e. Not keeping 
integration history across branches, what is a real pain to work with I 
guess.)

JMTC,
Alen


----- Original Message ----- 
From: "Jon Watte (ODE)" <hplus-ode at mindcontrol.org>
To: <aspirin at ntlworld.com>
Cc: "ode" <ODE at q12.org>
Sent: Thursday, June 30, 2005 13:07
Subject: Re: [ODE] From unstable to trunk...


>
> Is it time to change to something like Perforce or Subversion, which 
> tracks specific related change sets? It's much easier to integrate "this 
> particular patch" with those tools.
>
> tigris.org is a hosting site that lets you host on Subversion for free, 
> btw. (I don't know where SourceForge is at WRT Subversion project hosting)
>
> Cheers,
>
>              / h+
>
>
> Adam D. Moss wrote:
>> Hi all.
>>
>> I have the ability to check things into the trunk, and
>> I'm relatively awake lately.  We should start moving some
>> of the 'proven' patches from UNSTABLE to trunk before UNSTABLE
>> just becomes an irreconcilable fork and dumping pile.
>>
>> I haven't been tracking UNSTABLE myself, so if someone wants
>> to point out (or much better, isolate and mail a patch to me)
>> some good candidates for merging to trunk, that would be
>> good.  I'm mainly interested in merging stuff to trunk which
>> generally improves the stability and quality of code, so I'm
>> reluctant to be moving 'feature' patches to the trunk at
>> this point unless they're well-proven.
>>
>> ta,
>> --adam
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode
> 



More information about the ODE mailing list