Hi all,
We often checkout using a sticky tag, so that
developers can work with
baselines of code.
Normally, checkins on files or directories with a
sticky non-branch tag
are disabled, which is correct.
However, we have found out that sometimes commit on
these sticky tags succeed, because
Paul Gelderblom \(ptok\) writes:
This is a multi-part message in MIME format.
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
However, we have found out that sometimes commit on these sticky tags
succeed, because CVS somewhere in the process
Greg Woods:
In CVS the release number of RCS-Id is like any useless and almost
atrophied organ -- however it's impossible to give it up without
also giving up backwards compatability of the internal repository
structure.
It also is necessary as a magic cookie - an otherwise meaningless
but
[ On Tuesday, December 2, 2003 at 18:04:35 (-0800), Mark D. Baushke wrote: ]
Subject: Re: Problems with uncommitted working directories, from home and work.
I suppose you could also consider the Unison File Synchronizer (see
http://www.cis.upenn.edu/~bcpierce/unison/ for details) as a way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg A. Woods [EMAIL PROTECTED] writes:
[ On Tuesday, December 2, 2003 at 18:04:35 (-0800), Mark D. Baushke wrote: ]
Subject: Re: Problems with uncommitted working directories, from home and work.
I suppose you could also consider the Unison
[ On Wednesday, December 3, 2003 at 12:36:35 (-0600), [EMAIL PROTECTED] wrote: ]
Subject: Re: CVS Version CHange
Could be. The RCS revision number looks too much like a standard sort
of release designation, and that leads to trouble. It appears to
contain more information than is needed to
