On Aug 22, 2009, at 4:00 PM, Reinier Lamers wrote:
If
this is in fact the case, the only way that one could convert a darcs
repository which had spawned many branches (which were up to that
point compatible with one another), would be to merge all of the
branches to one main repository and subsequently convert? This
process basically forces merging of branches before conversion.
That, too, is correct.
In the process of merging repositories for later "unpeeling" into
separate branches (once the conversion is completed), is there any way
to automate, or at least expedite the finding of patches which we
don't want in our main repository (those which will be moved to non-
production branches)? Aside from doing regular expression searches,
are there any more explicit means of identifying patches (by ID
perhaps)?
Thank you for your help!
-lev
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
