Sorry - Having never done *software* releases with CVS myself, I misphrased my
query. What I really meant was 'cvs export'. In other words, we do a 'cvs
export' of a tagged branch as part of our release process. I wanted to capture
the tag name of the cvs-*exported* branch by processing a CVS
At 17:03 +1000 4/8/02, Sonam Chauhan wrote:
Sorry - Having never done *software* releases with CVS myself, I
misphrased my query. What I really meant was 'cvs export'. In other
words, we do a 'cvs export' of a tagged branch as part of our
release process. I wanted to capture the tag name of
In [EMAIL PROTECTED] Sonam Chauhan [EMAIL PROTECTED] writes:
Sorry - Having never done *software* releases with CVS myself, I misphrased my
query. What I really meant was 'cvs export'. In other words, we do a 'cvs
export' of a tagged branch as part of our release process. I wanted to capture
Thanks Pierre - $Name$ was just what we wanted.
Kind regards,
Sonam
In [EMAIL PROTECTED] Sonam Chauhan [EMAIL PROTECTED]
writes:
Sorry - Having never done *software* releases with CVS myself, I misphrased my
query. What I really meant was 'cvs export'. In other words, we do a 'cvs
export'
Hmm, Maybe this reply does not address the original post.
I think the reason why *release* was in quotes is to not imply the
release command but rather an individual's release process. I too am
interested in how to expand a label or symbolic tag into a file. This
would be handy for
