Hi again Eric, On Aug 25, 2010, at 2:22 AM, Eric Kow wrote: > One scenario where this may be safe is if you can make sure that the > history of the main repo is a prefix of the main-branch repo. You can > do this with > > darcs get main tmp > darcs pull --repo tmp main-branch > > Then converting main and tmp separately should work > >> In testing this with a push, darcs failed with an error messsage which >> I took to prove just that. > > Could I see that error message, out of interest? > > Meanwhile, hopefully I've not said something silly! Somebody from the > list will likely pipe up if I've made a mistake in my thinking
So as an update, the errors which I mentioned do not occur with the statically-linked binary (2.4.4) available from the darcs site. We went the circuitous route with the sending and applying of patches nevertheless (even though a simple 'push' seems to work as well). The question now, is, what sort of problems exist when two repos (based off of common patches) get converted, and have their patches intermingled? So far, I've not found any functionality issues, but I am not quite sure what to even be looking for. Darcs seems to be plugging away and working fine so far. thanks, -lev _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
