Any intent to support the concept of thread with inheritance in Mercurial or derivatives?

Pierre Rouleau prouleau001 at gmail.com
Tue Jan 1 22:43:41 CST 2008


Mark A. Flacy wrote:
> On 2008.01.01 21:48, Pierre Rouleau wrote:
>> Hi all,
>>
>> I recently stumbled on an article describing the capabilities of  
>> AccuRev
>>   inheritable threads ( http://www.daveonscm.com/ ).
>>
>> The article describes how AccuRev's streams simplifies the
>> branching/merging work.
> 
> Nice as long as you don't have multiple "tasks" touching the same files.
> 
> 
I am not that familiar with AccuRev and the facilities that its threads 
offer.  However, the thread system with its concept of inheritance, 
seems a good idea to replicate info automatically.  They have different 
types of threads with different behaviours related to what is allowed to 
change.

I am assuming that the changes allowed in the parent would be under 
control.  Something someone would have to do anyway when pulling changes 
from several other repositories.

However, if there were any 'children' repository to that single 'parent' 
repository, no explicit pull/update would be required: maybe just an 
update or something.

Have you (anyone) worked with AccuRev or any other SCM that support the 
concept of inheritance with streams?

--

Pierre Rouleau



More information about the Mercurial mailing list