From: Godmar Back (gback@cs.utah.edu)
Date: Tue Dec 22 1998 - 02:34:14 EST
So, when I check in that jit fix, it won't show up in the NEW_STRINGS
branch. I would have to check that branch out, apply the patch, check it
in. Or I dig in the cvs manual and find some magic merge command that
applies the change to the branch.
This is why I hate CVS (besides similarly complex pieces of software including,
but not limited to latex, emacs and autoconf). It is countless times that
I tried these cvs maneuvers and they failed with cryptic messages, but of
course, after four hours I realized that either file permissions where wrong,
I had accidentally deleted an configuration file, or simply had the wrong
cvs client version.
My point: get that NEW_STRINGS branch eliminated as fast as possible.
If you feel confident enough that it runs, merge it and nuke it.
I could see us using branches if we did a Linux-like release cycle,
with branches for ``stable'' releases. But other than that, I'd
personally avoid them.
For now, would you take responsibility for keeping that NEW_STRINGS
branch up-to-date?
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:27 EDT