There is already an Eggs Unlimited 4 page, which will have to be modified so that the links point to the release 4 egg documentation. This is why I proposed (and implemented) two post-commit scripts, so that the release 4 script can be changed without affecting the one for release 3. I agree that moving the release 3 eggs would possibly break some links, but I don't see how this could be done without at least modifying the post-commit script for release 4 eggs.
-Ivan "felix winkelmann" <[EMAIL PROTECTED]> writes: > Would it? Probably, but this release 4 documentation would not > be for public use, only to keep documentation pages up to date > until chicken-4 is released (basically just for direct access via > svn). Moving all the existing pages to a subdir will possibly lead > to even more confusion (and destroy links, etc.). > > I'm not insisting on any particular solution, but I'd like not to > mess with egg-post-commit any more, and we need a place > to put egg documentation until the next release. _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
