I'm not sure if this is a known problem (or even if
it's recognized as being a feature rather than a bug)
but here it goes:
cvs annotate does not use sticky tag. One would
have to use the -r option in order to annotate a
particular version.
Noel
Hi,
I installed cvs on Solaris 8 from sources(cvs-1.11.1p1).
In order to start the cvspserver automatically, I added the following
line to /etc/ined.conf:
cvspserver stream tcp nowait root/usr/local/bin/cvs
--allow-root=/export/home/cvs -f pserver
And following line to
On Mon, 26 Aug 2002, Noel Yap wrote:
I'm not sure if this is a known problem (or even if
it's recognized as being a feature rather than a bug)
but here it goes:
cvs annotate does not use sticky tag. One would
have to use the -r option in order to annotate a
particular version.
Using
--- Kaz Kylheku [EMAIL PROTECTED] wrote:
On Mon, 26 Aug 2002, Noel Yap wrote:
I'm not sure if this is a known problem (or even
if
it's recognized as being a feature rather than a
bug)
but here it goes:
cvs annotate does not use sticky tag. One
would
have to use the -r option
--- Noel Yap [EMAIL PROTECTED] wrote:
Unless our definitions of Sticky Tag differ, it
sounds like we agree on what cvs ann /should/ do.
Upon reviewing my definition of Sticky Tag, I'm
embarassed to find that it's wrong.
So, restating the problem: cvs ann is annotating the
head revision of the
On Mon, 26 Aug 2002, Noel Yap wrote:
--- Kaz Kylheku [EMAIL PROTECTED] wrote:
Using the sticky tag would be unsatisfactory in the
case that it's a
branch tag, because you would be annotating from the
branch tip.
[ snip ]
I don't understand.
Currently (from what I'm seeing), cvs
It looks like this is another reason to make the distinction between
sticky branch and version tags. With branch tags, I agree with Kaz.
With version tags, I agree with Noel.
--- Forwarded mail from [EMAIL PROTECTED]
On Mon, 26 Aug 2002, Noel Yap wrote:
I'm not sure if this is a known
--- Paul Sander [EMAIL PROTECTED] wrote:
It looks like this is another reason to make the
distinction between
sticky branch and version tags. With branch tags, I
agree with Kaz.
With version tags, I agree with Noel.
OTOH, if it works against the working revision, it'll
be correct whether
Mahantesh writes:
cvspserver stream tcp nowait root/usr/local/bin/cvs
--allow-root=/export/home/cvs -f pserver
You left out argv[0] -- that should read:
cvspserver stream tcp nowait root /usr/local/bin/cvs cvs
--allow-root=/export/home/cvs -f pserver
What is the best way to lock a branch? Should I use
the admin -l option? I tried this and couldn't get it
to work. I have also seen some previous post
suggesting to create a #commitinfo file. We would
like to be able to lock a complete branch, so that
developers can not accidentally commit
On Mon, 26 Aug 2002, Pat Young wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How about:
``Please don't commit to this branch until told
--- Forwarded mail from [EMAIL PROTECTED]
On Mon, 26 Aug 2002, Pat Young wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How about:
On Mon, 26 Aug 2002, Paul Sander wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How about:
``Please don't commit to this branch
--- Forwarded mail from [EMAIL PROTECTED]
On Mon, 26 Aug 2002, Paul Sander wrote:
Date: Mon, 26 Aug 2002 14:12:04 -0700 (PDT)
From: Pat Young [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [info-cvs] Locking a branch
What is the best way to lock a branch? Should I use
How
Hi,
We are successfully using the CVS watch option for monitoring common
modules. In order to reduce the amount of emails the user has to open, I
would like to send out notifications that have a variable subject line (e.g.
the username or filename) instead of sending out notifications with the
15 matches
Mail list logo