Hi Mark Stosberg! Welcome back! I'm doing something similar to what you suggest for some repositories hosted by allmydata.org:
http://allmydata.org/source/tahoe/trunk vs. http://allmydata.org/source/tahoe/trunk-hashedformat I have a post-apply hook in trunk which does a darcs push -a to trunk- hashedformat (using the locally installed darcs-2 executable). Now people who have only darcs-1 executables can push and pull from the "trunk" repository. People who have darcs-2 executables can pull from the trunk-hashedformat repository, but they have to push to the trunk repository, so that their patches will be visible to people using darcs-1 executables. Okay, so far so good, but in practice what happened is that after this worked for a couple of months, then we ran into some bug with darcs-1-executables (I forget what it was, sorry), and everyone stopped using darcs-1 executables. So now this infrastructure that I have set up is somewhat vestigial. Hopefully it still serves its purpose if there are people out there who have darcs-1 installed and who want to fetch the allmydata.org "Tahoe" source code. Regards, Zooko _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
