Ick. I hate keyword expansions. The minute you ever merge
between branches you have to deal with those keywords.
donald
On Sat, Nov 01, 2003 at 02:18:45PM +0100, Spiro Trikaliotis wrote:
Hello,
On Fri, Oct 31, 2003 at 04:53:33PM -0500, Robert Clark wrote:
If you are not too worried a
Todd Denniston [mailto:[EMAIL PROTECTED] wrote:
Jim.Hyslop wrote:
echo ^RCS file:filerev
echo ^revision filerev
cvs log -rCURRENT_TAG | grep -f filerev
I think the above may give you some false positives, the
files in the Attic
(dead don't have the tag) lists all revs in the
Jim.Hyslop wrote:
Katherine King [mailto:[EMAIL PROTECTED] wrote:
SNIP
Now, having said all that, if they want to see if something's changed, they
can use the diff command:
cvs diff -rPREVIOUS_TAG -rCURRENT_TAG filename
If diff says nothing, then the file has not changed.
To get
Well cvs up -kk -j branch-tag-1 -j branch-tag-2 seems to work
okay for me to avoid problems with merging the keywords (I think we've
only used $Id$, though).
-- Jamie Wellnitz
On Mon, Nov 03, 2003 at 09:05:49AM -0500, Donald Sharp wrote:
Ick. I hate keyword expansions. The minute you ever
Hi,
I am pretty much a beginner to CVS, but somehow becoming the expert on the
team, and this is now causing me to need to ask for some help. We have a
CVS repository, and we are working with branches and tags, no problem. But
we need a little more information about revision numbers for the
Why do you need this? What is important is the label!
If you can't convince them that it's not terribly important
pull a workspace over the release label and do a cvs status -R
and parse the output.
donald
On Fri, Oct 31, 2003 at 03:56:47PM -0500, Katherine King wrote:
Hi,
I am pretty much
: Donald Sharp [mailto:[EMAIL PROTECTED]
Sent: October 31, 2003 4:11 PM
Subject: Re: revision/version numbers
Why do you need this? What is important is the label!
If you can't convince them that it's not terribly important
pull a workspace over the release label and do a cvs status -R
and parse
: revision/version numbers
Why do you need this? What is important is the label!
If you can't convince them that it's not terribly important
pull a workspace over the release label and do a cvs status -R
and parse the output.
donald
On Fri, Oct 31, 2003 at 03:56:47PM -0500, Katherine
: Re: revision/version numbers
Why do you need this? What is important is the label!
If you can't convince them that it's not terribly important
pull a workspace over the release label and do a cvs status -R
and parse the output.
donald
On Fri, Oct 31, 2003 at 03:56:47PM -0500, Katherine
PROTECTED]'
Subject: Re: revision/version numbers
Why do you need this? What is important is the label!
If you can't convince them that it's not terribly important
pull a workspace over the release label and do a cvs status -R
and parse the output.
donald
On Fri, Oct 31, 2003
automatically, with a script, this will help. :)
-Original Message-
From: Donald Sharp [mailto:[EMAIL PROTECTED]
Sent: October 31, 2003 4:25 PM
To: Katherine King
Cc: '[EMAIL PROTECTED]'
Subject: Re: revision/version numbers
How does this confirm that you are or aren't using a old version
Labels are not immutable; they can be moved around. Some shops deliberately
use floating labels, e.g. to identify the latest sources eligible for build.
This cuts down on clutter under several methodologies. Under such conditions,
pulling from a specific (floating) label may NOT pull the
Katherine King [mailto:[EMAIL PROTECTED] wrote:
It doesn't as such - the tester has to trust us that far, but
this is still
something that they are demanding.
I'm still not clear *why* these testers - who you said earlier are not
programmers - have to verify whether a file has actually changed
At 16:10 2003-10-31 -0500, Donald Sharp wrote:
Why do you need this? What is important is the label!
If you can't convince them that it's not terribly important
pull a workspace over the release label and do a cvs status -R
and parse the output.
Or, list the various CVS/Entries files. Let
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
Labels are not immutable; they can be moved around. Some
shops deliberately
use floating labels, e.g. to identify the latest sources
eligible for build.
Then the label should clearly indicate it's the latest version. A version
handed off to
Jim.Hyslop wrote:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
Labels are not immutable; they can be moved around. Some
--[clip]--
Then the label should clearly indicate it's the latest version. A version
handed off to QA is not the latest version, and should have a unique label.
--- Forwarded mail from [EMAIL PROTECTED]
Jim.Hyslop wrote:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
Labels are not immutable; they can be moved around. Some
--[clip]--
Then the label should clearly indicate it's the latest version. A version
handed off to QA is not the latest
--- Forwarded mail from [EMAIL PROTECTED]
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
Labels are not immutable; they can be moved around. Some
shops deliberately
use floating labels, e.g. to identify the latest sources
eligible for build.
Then the label should clearly indicate it's
On Fri, 2003-10-31 at 16:31, Katherine King wrote:
It doesn't as such - the tester has to trust us that far, but this is still
something that they are demanding. It came up today because we had to do a
deploy from a branch (most are off the main branch). If it is possible to
extract the
19 matches
Mail list logo
