On Fri, Jan 11, 2008 at 08:43:13PM +0200, Tristan Seligmann wrote: > * David Roundy <[EMAIL PROTECTED]> [2008-01-11 12:42:31 -0500]: > > Well, currently the conversion to darcs-2 requires a bottleneck, in which > > only *one* repository is converted (i.e. all other branches get lopped > > off). I think this is reasonable, as the transition to darcs-2 is always > > going to require a "flag day" in any case, when a project switches > > repository format, and I haven't been able to come up with a realistic > > scenario in which this would pose a real problem. > > On some of my projects we have long-running branches that are never > merged back into the "mainline" (although changes from the mainline are > pushed out to these branches); this isn't an issue for me anymore, > because these projects will have been retired before darcs-2 is even > released, but perhaps other people have this kind of workflow.
As long as there's only one such branch, there's no problem (unless there are conflicts): you just convert that branch, and then reconstruct mainline by obliterating all the patches that shouldn't be there. -- David Roundy Department of Physics Oregon State University
signature.asc
Description: Digital signature
_______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
