cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pier Fumagalli <p...@betaversion.org>
Subject CVS repository changes... (and what's left to do)
Date Thu, 27 Feb 2003 03:04:01 GMT
Ok, got a few extra hours tonight, so I just did it! :-)

The old "xml-cocoon2" repository has been moved to "cocoon-2-historic", but
a symlink with the old name is preserved so that you can do those nifty "cvs
diff" and see what _you_ changed in there...

Same thing happened for "xml-cocoon", renamed to "cocoon-1", but preserving
the old name as a symlink, and "xml-cocoon2-apps" renamed to "cocoon-2-apps"
(old name preserved, but should I just blast this? Nicola-Ken?)...

Two new repositories have been created, containing the latest CVS versions
of 2.0 and 2.1, those are called, respectively, "cocoon-2.0" and
"cocoon-2.1"... Do a checkout and tell me there's something wrong with them.

If you were working on something in the "old" repository, the easiest way to
do this is by doing the following:

# cd ~/checkouts/xml-cocoon2
# cvs diff -u3 > /tmp/patch
# cd ~/checkouts
# cvs co cocoon-2.1
# cd cocoon-2.1
# cvs update -Apd
# patch -p0 < /tmp/patch
# rm -f /tmp/patch

Windows folks, please translate the above POSIX shell commands in something
suitable in your environment! :-)

Now, the only things left to do are removing the symlinks with the old names
once you're all happy with the changes, and fixing up various bits in the
mail system, but I can do that in a few days, once everyone has its local
copy of Cocoon checked out right on his machine (like, me... Gotta update
the copies at work tomorrow)...

Now, call me "fascist" :-) if you want, but to avoid people to commit back
to the old repository names, I've removed YOU ALL karma to the old
repositories... I call it "defensive administration" :-) It's a concept that
Brian taught me back in 1997... If you want to commit, you'll have to use
the new repository names (so, as outlined above, do the patch against the
old repo, checkout the new one, apply the patch, and commit)...

Note, on my Netra-T1, now updating the whole repository for Cocoon 2.1 takes
less than 1/3 of the time it required before! :-) :-)

Have fun! :-)

    Pier (yes, in case of emergencies, we can revert back in 15 minutes)


Mime
View raw message