On Jan 20, 2008 7:41 AM, Ivan Raikov <[EMAIL PROTECTED]> wrote: > > Am I the only one who finds this scheme (ha!) confusing? Is it > possible to use some Subversion trick so that a commit to a top-level > egg directory automatically does copy/commit in the latest release > branch also? This will really help absent-minded people like myself > to make sure that new egg releases are committed to the current > Chicken release branch.
I agree that it's confusing, but to minimize disruption by the branching process (and to avoid hacking too deeply into some pretty gnarly and subtle post-commit scripts) we have kept the old structure and just added a branch on top of it. When some time has passed, the toplevel eggs will be moved into a release/2 branch. cheers, felix _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
