(I hate not being able to reply to the messages, but either I'm having
problems getting email from the list or my filters rae eating the
messages. Could be worse: they could be spitting out nastygrams ;^))
Greg:
I do agree with the bit about not allowing code out of control without a
tag. In
[ On Friday, April 20, 2001 at 08:49:34 (-0500), David D. Hagood wrote: ]
Subject: Re: $Name $ in branches
Because I often have developers working on several different "things" at
once. For example, I may be working on signal processing, and in a
seperate branch working on
[EMAIL PROTECTED] (CVS-II Discussion Mailing List) wrote:
Huh? Why doesn't the $Author keyword (part of $Id, BTW), work for you
then?
Because I often have developers working on several different "things" at
once. For example, I may be working on signal processing, and in a
seperate branch
I'm a little confused by an aspect of CVS:
If I have a file that contains the $Name: $ keyword, and that file is
checked out under a normal, non-branch tag FOO, the keyword will be
expanded as $Name: FOO$. However, if the tag is a branch, the keyword
won't be expanded.
Is there some logic
), David D. Hagood wrote: ]
Subject: $Name $ and branches
Is there some logic behind this behavior? For some of what I am doing,
I'd really like to have the $Name$ be replaced with the branch tag.
In CVS $Name is really only intended to be used with "cvs export -kv".
I.e. it's there
[ On Thursday, April 19, 2001 at 11:01:27 (-0500), David D. Hagood wrote: ]
Subject: $Name $ and branches
Is there some logic behind this behavior? For some of what I am doing,
I'd really like to have the $Name$ be replaced with the branch tag.
In CVS $Name is really only intended
I disagree with Mr. Woods on this: adding the branch ID to a build makes
sense in my environment: I have several developers, each working on
their own branch of an embedded system. As needed, the load their code
into target systems for development. Since the number of developers is
larger
[ On Thursday, April 19, 2001 at 16:12:25 (-0500), David D. Hagood wrote: ]
Subject: $Name $ in branches
I disagree with Mr. Woods on this: adding the branch ID to a build makes
sense in my environment: I have several developers, each working on
their own branch of an embedded system
I haven't tried it, but it looks like the $State$ keyword could provide the
functionality you're looking for.
See:
http://www.cvshome.org/docs/manual/cvs_12.html#SEC98
and
http://www.cvshome.org/docs/manual/cvs_16.html#SEC120
Jerry
___
Info-cvs
[ On Thursday, April 19, 2001 at 18:19:04 (-0700), Jerry Nairn wrote: ]
Subject: RE: $Name $ in branches
I haven't tried it, but it looks like the $State$ keyword could provide the
functionality you're looking for.
Take care because $State is also used internally in CVS.
Probably the most
10 matches
Mail list logo
