> 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).
Thanks. That's just the kind of story I was hoping for.
One more confirmation:
In this kind of scenerio, I think it should *not* be necessary to recreate the
repos managed by darcs 1.x, because the repo they are talking to won't be
changing. We'll be creating a compatible darcs-2 repo that parallels it.
To make my scenario easily to visualize, we'll have this:
Dev Box (Darcs 2 installed)
alpha-darcs-2
alpha-darcs-1 ( Managed automatically through a post-hook
- Mark
- Matt
- other devs
-----------
Production Box (Darcs 1 installed )
beta-darcs-1
production-darcs-1
####
The three "darcs-1" repos will remain the same, but all the developers and a
new copy of the "alphasite" will now be in darcs-2 format.
Patches normally only flow from alpha to beta and then production, and rarely
ever in the reverse direction.
Mark
_______________________________________________
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
