On Thu, Oct 29, 2009 at 4:51 PM, Garrett D'Amore <garr...@damore.org> wrote:
>>>
>>> I don't think a child will be as easy to work with, if only because I'll
>>> constantly be doing merges.
>>>
>>
>> This seems like a fallacy. You only need to merge when you decide that
>> you want to base your software on a newer snapshot, much like you'd need
>> to do the same "merging" if you were to grab new versions of the random
>> collection of header files you mention above.
>>
>
> Its just an hg update of a clone if the clone sits alongside. hg merge on
> the other hand, pollutes the revision history, and is something I'd like to
> avoid.
>
I found rebasing my branch/repo against evolving parent repository is
very efficient in similar cases.
In fact that is how I do my own OpenSolaris (and other) software development.
--
Regards,
Cyril
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
