I'm getting an error message on trying to commit:
cvs server: sticky tag `WCGCPG-1-0' for file `init.blk' is not a branch
I've only just started playing around with tags and have obviously missed
something. I created the referenced tag in the top level of my checked out
work area, thus: cvs t
Hi,
I am trying to understand how sticky tags
work (or they are useful). One way is to
identify branches, this seems pretty clear.
The other way is (according to the manual),
to allow a user to avoid updating a portion
of a larger tree into his working copy.
I then tried to imagine a
Hello Everyone,
... Yes, I searched the archives!
Here's my situation:
1) I have cvs repository for a project, and I inadvertently included a
bunch of .mod files in it (the source code is in fortran-90 and .mod
files are generated at compile-time from source code, so I don't really
need them in
Scott Holmes writes:
>
> I'm getting an error message on trying to commit:
> cvs server: sticky tag `WCGCPG-1-0' for file `init.blk' is not a branch
``cvs update -A'' will remove the sticky tag and return your working
directory to the tip of the trunk so that you can do checkins.
-Larry Jones
>From: Scott Holmes [mailto:[EMAIL PROTECTED]]
>Sent: Friday, March 30, 2001 9:46 AM
>I'm getting an error message on trying to commit:
>cvs server: sticky tag `WCGCPG-1-0' for file `init.blk' is not a branch
And as you know it is not on a branch. A tag which is not a branch tag is
intended to
--- irina sturm <[EMAIL PROTECTED]> wrote:
> I want to
> keep up with the modifications other users
> perform on file_1, but not on file_2.
> I want to incorporate the other users
> modifications on file_2 only when I've
> finished my own modifications.
> Then the sequence of commands to achiev
[EMAIL PROTECTED] wrote:
>
> --- irina sturm <[EMAIL PROTECTED]> wrote:
> > I want to
> > keep up with the modifications other users
> > perform on file_1, but not on file_2.
> > I want to incorporate the other users
> > modifications on file_2 only when I've
> > finished my own modifications.
>
, but just doing the same as for file_1.
> In which case also I can't understand what the
> sticky tag is useful for.
you can run cvs update all day long and CVS will not bring in new changes for
files checkedout on non-branch sticky tags, like your file_2. So you can
continue to run cvs update
Hi Irina,
Perhaps it could be a good idea to have a look at this.
http://cvsbook.red-bean.com/cvsbook.html#Getting_Snapshots__Dates_And_Tagging_
You surely will understand why sticky tags are, and how they works !
(Buying the book is also a good idea)
Edouard
he
> > other users' modifications before finishing
> > with my own, but just doing the same as for file_1.
> > In which case also I can't understand what the
> > sticky tag is useful for.
>
> you can run cvs update all day long and CVS will not bring in new ch
--- irina sturm <[EMAIL PROTECTED]> wrote:
> I don't understand: if I am doing what you say,
> I am not preserving myself of integrating the
> other users' modifications before finishing
> with my own, but just doing the same as for file_1.
To do this (i.e. make and commit changes without (yet)
i
n Behalf Of
> Eric Siegerman
> Sent: Thursday, 12 July 2001 7:22 a.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Sticky tags
>
>
> --- irina sturm <[EMAIL PROTECTED]> wrote:
> > I don't understand: if I am doing what you say,
> > I am not preserving myself o
Thank you very much, Eric, for your answer.
This helps to understand better, and it is
somehow the way I saw the problem myself.
Irina.
[EMAIL PROTECTED] wrote:
>
> --- irina sturm <[EMAIL PROTECTED]> wrote:
> > I don't understand: if I am doing what you say,
> > I am not preserving myself of
On Thu, Jul 12, 2001 at 08:26:24AM +1200, Chris Cameron wrote:
> We use non branch sticky tags for preserving 'contours' through our code
> (e.g. release 1.0, integration build 2, etc.). This is very usefull for
> determining changes from one 'release' to another an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ed Zaron <[EMAIL PROTECTED]> writes:
> Hello Everyone,
>
> ... Yes, I searched the archives!
>
> Here's my situation:
>
> 1) I have cvs repository for a project, and I inadvertently included a
> bunch of .mod files in it (the source code is in fort
hello Do I understand it correctly, your checking out a project from cvs,
that has a given tag. and then you would like to delete some files ??
If so I would really like to know what cvs version your using. Because I
have a opposite situation. Where I do not want to delete tagged files. But
atm im
Mark D. Baushke writes:
>
> Your basic problem is that 'cvs rm -f' tells cvs to try to force the
> removal, so you won't get the normal error message:
>
> cvs remove:cannot remove file `barotropic.mod' which has a sticky date of
> `2004.11.03.08.00.00'
>
> which you might otherwise have receive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Jones <[EMAIL PROTECTED]> writes:
> Mark D. Baushke writes:
> >
> > Your basic problem is that 'cvs rm -f' tells cvs to try to force the
> > removal, so you won't get the normal error message:
> >
> > cvs remove:cannot remove file `barotropic.
Hi Mark and Henrik:
Mark, I tried your suggestion, but it didn't seem to work. I have
reproduced the transcript below:
[c-160-149-198:~/Desktop/X/src] ezaron% cvs add barotropic.mod
cvs add: barotropic.mod should be removed and is still there (or is
back again)
[c-160-149-198:~/Desktop/X/src]
Ed Zaron writes:
>
> [c-160-149-198:~/Desktop/X/src] ezaron% cvs add barotropic.mod
> cvs add: barotropic.mod should be removed and is still there (or is
> back again)
That indicates that you somehow managed to get a local barotropic.mod --
delete it and then do the add followed by the update -
ost recent. I'm confused as to what the
'state' of everything is.
Today, as I go to check in several files, I did a cvs update. No problem.
Then I tried to commit my changes and I got an error. I'd fix the "above
errors first", but I don't know how to except my
FYI, I'm not sure if this is a bug or a feature, but
"cvs ann" is ignoring sticky tags.
Noel
__
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com
___
I
Can someone please email me back at [EMAIL PROTECTED] and tell me
Sticky tags vs tags in CVS for dummy.
Should I use tags or Sticky tags??
Run:
cvs update -A
This will remove the sticky tags holding you to a particular release.
donald
On Mon, Jan 07, 2002 at 05:12:44PM -0800, Schwenk, Jeanie wrote:
> I'm using cvs 1.11 on hpux.
>
> I tagged the Aug 21 release with the tag Release_Aug21_2001. Just a plain
> ta
On Mon, Jan 07, 2002 at 05:12:44PM -0800, Schwenk, Jeanie wrote:
> Today, as I go to check in several files, I did a cvs update. No problem.
cvs update -A
mrc
--
Mike Castle [EMAIL PROTECTED] www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Wa
Yes, the sticky tags just mean that the tree you were working in
was pulled (or the one you used to create) the Release_Aug21_2001 tag,
they
haven't been "put on every file" in any different way than
when you tagged the tree before you left. Developers that have been
working in s
Schwenk, Jeanie writes:
>
> While I was out for several weeks, the vendors who happen to be on the other
> side of the world put a sticky tag on every file, including those I am
> editing.
No they didn't -- sticky tags are in your working directory, not the
repository. Most
Thanks everyone for their responses but I need some additional
clarification.
1) I checked out all my files prior to the vendors putting the sticky tags
on. So why are the sticky tags effecting me? Is it because commit verifies
that the selected files are up to date with the current
> From: Schwenk, Jeanie [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 08, 2002 10:07 AM
> Thanks everyone for their responses but I need some additional
> clarification.
You're demonstrating ignorance of how tags are used in cvs. Please read the
reply you got from Larry Jones, and look
Jeanie,
You said in your email yesterday that *you* created the
Release_Aug21_2001 tag.
The only way *you* can have a working copy of the tree
listing sticky tags of Release_Aug21_2001 is if *you*
either 1) did a fresh "cvs co -r Release_Aug21_2001 "
to create your tree or 2) did
I missed the original, but the followup had enough quoted text...
>donald
>On Mon, Jan 07, 2002 at 05:12:44PM -0800, Schwenk, Jeanie wrote:
>> I'm using cvs 1.11 on hpux.
>>
>> I tagged the Aug 21 release with the tag Release_Aug21_2001. Just a plain
>> tag.
>>
>> While I was out for several
"Schwenk, Jeanie" <[EMAIL PROTECTED]> writes:
>Thanks everyone for their responses but I need some additional
>clarification.
>1) I checked out all my files prior to the vendors putting the sticky tags
>on.
We all think the vendor did no such thing.
>So wh
On Tue, 16 Jul 2002, Noel Yap wrote:
> FYI, I'm not sure if this is a bug or a feature, but
> "cvs ann" is ignoring sticky tags.
I see what you mean; it behaves analogously to log, just
working on the RCS file. It would make a certain amount
of sense to pass in the sticky.
--- Kaz Kylheku <[EMAIL PROTECTED]> wrote:
> On Tue, 16 Jul 2002, Noel Yap wrote:
>
> > FYI, I'm not sure if this is a bug or a feature,
> but
> > "cvs ann" is ignoring sticky tags.
>
> I see what you mean; it behaves analogously to log,
> just
On Tue, Jul 16, 2002 at 09:27:23AM -0700, Noel Yap wrote:
> --- Kaz Kylheku <[EMAIL PROTECTED]> wrote:
> > On Tue, 16 Jul 2002, Noel Yap wrote:
> >
> > [...] what if you are sticky to something that is a moving target,
> > i.e. a branch? Should annotate then start with the
> > closest repository
ry Invalid
This was unexpected for me. Of course the file is still in the
repository, but it doesn't have the tag that was specified in the cvs
update command.
Of course I can write a script to go back and cvs update -A these
files with nonexistent sticky tags, but it isn't a very efficient
Hi,
I'm using CVS version 1.10.7 on Windows (not using the client/server model).
I have a CVS project that is made of some directory tree, where the topmost
directory does not contain any files:
root
subdir1
subdir2
...
The root directory of the project ("root") does not contain any fil
On Mon, Feb 25, 2002 at 06:54:17PM +, Chuck Taylor wrote:
> I discovered last week that if I run
>
> cvs update -f -r
>
> in a working directory, then files that don't have
> defined are checked out from the main trunk, as the -f option directs.
> However, CVS still applies the sticky
Eric Siegerman wrote:
>
> On Mon, Feb 25, 2002 at 06:54:17PM +, Chuck Taylor wrote:
> > I discovered last week that if I run
> >
> > cvs update -f -r
> >
> > in a working directory, then files that don't have
> > defined are checked out from the main trunk, as the -f option directs.
> >
On Mon, 25 Feb 2002 14:49:38 -0500, Eric Siegerman
<[EMAIL PROTECTED]> wrote:
>...why are you only tagging some of the files? Just tag
>everything; then it won't be a problem.
We have preferred so far to create branches only on files that were
being modified in conjunction with a task because
On Tue, Feb 26, 2002 at 01:27:41PM +, Chuck Taylor wrote:
> On Mon, 25 Feb 2002 14:49:38 -0500, Eric Siegerman
> <[EMAIL PROTECTED]> wrote:
>
> >...why are you only tagging some of the files? Just tag
> >everything; then it won't be a problem.
>
>
> We have preferred so far to create branc
On Tue, 26 Feb 2002 15:34:25 -0500, Eric Siegerman
<[EMAIL PROTECTED]> wrote:
>On Tue, Feb 26, 2002 at 01:27:41PM +, Chuck Taylor wrote:
>> -- The recursive action of cvs tag puts a sticky tag on
>> directories themselves, which interferes with cvs add
>> ("-->Using per-directory
I have this example where I tag my stream at different point, but not as
branches:
MAIN Stream
Release1---Release2--Release3->
The tags are Release1, Release2, and Release3.
When I do a "cvs co -r Release1 myModule",
I can't check-in any files th
This distinction is really between plain tags versus branch tags; sticky
tags is just a user action that is "applied" to a plain/branch tag; kind of
like the distinction between Republican politician versus Democrat
politician and a user action that make one a corrupt Republica
When I'm reading articles/guides about CVS I notice that "removing sticky
tags" is often talked about.
I don't understand why you want to remove a sticky tag.
If (for example) you have files in a repository and they're
ready/checked/validated for release 1, then you tag t
I think you can simply create a branch tag over the top of Release1
e.g.
cvs co -r Release1 srctree
cd srctree
cvs tag -b Release1_Branch
cvs update -r Release1_Branch
give it a try on a test repository
Danial Islam wrote:
>I have this example where I tag my stream at different point, b
Danial Islam writes:
>
> When I do a "cvs co -r Release1 myModule",
> I can't check-in any files that I modified from it, it says the sticky
> tag is not on a branch.
>
> How would someone be able to checkin from a tagged part of the stream?
> Or would I have to create a branch from Release1 an
ECTED] On Behalf Of
Anand Graves
Sent: Friday, June 18, 2004 3:49 PM
To: [EMAIL PROTECTED]
Subject: Why should you want to remove sticky tags?
When I'm reading articles/guides about CVS I notice that "removing sticky
tags" is often talked about.
I don't understand why you wa
On Fri, 18 Jun 2004, Anand Graves wrote:
> Date: Fri, 18 Jun 2004 21:48:55 +0200 (CEST)
> From: Anand Graves <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Why should you want to remove sticky tags?
>
> When I'm reading articles/guides about CVS I notice tha
I think there are two aspects to the "removing sticky tags" issue:
- Removing tags
- Removing the "stickiness" of tags
Removing tags is desirable to clean up the output of "cvs log" if a lot
of temporary tags are created. An example of this is when built sources
50 matches
Mail list logo
