Hello,
I have a problem using rdiff to check it a tag exists for a given
module.
I created 2 modules 'c' and 'd', and I want to know if these modules are
tagged with 'K2'
[EMAIL PROTECTED]:/tmp$ cvs rdiff -rK2 -rK2 c
cvs [server aborted]: no such tag K2
[EMAIL PROTECTED]:/tmp$ cvs rdiff -rK2 -r
> I have a problem using rdiff to check it a tag exists for a given
> module.
I have this problem with cvs version 1.11.1p1 on AIX 4.3, and cvs
version 1.11.6 on AIX 5
--
Aldo Tendron
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/ma
Could one use:
cvs rtag -r oldname newname .
"Larry Jones" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Yes, use "cvs admin -n" to create the new tag pointing to the same...
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu
Lazy Dumbness writes [in excruciatingly long lines with very bad
formatting]:
>
> Up is a section of CVS manual.I can't understand it really.first,it
> said that 'if you have a checked-out copy of sources...',what is the
> release reverion of this source?
In most cases it doesn't really matter.
>
On Thu, 13 Nov 2003, Aldo TENDRON wrote:
> Hello,
> I have a problem using rdiff to check it a tag exists for a given
> module.
> [...]
Hehe, I've tried that before, and stumbled with the same problem.
The reason is, I think, when a tag has been successfully used it
ends up in the cache file CVSR
> Then you rdiffed on c, which contains the tag, so the tag is
> added to val-tags. The second time you check on d, the tag
> "exists", even though the diff will be obviously empty.
So, if a tag is successfully used one time, cvs assumes that it exists
for all modules ? Is this a cvs issue, or is
Aldo TENDRON [mailto:[EMAIL PROTECTED] wrote:
> > Then you rdiffed on c, which contains the tag, so the tag is
> > added to val-tags. The second time you check on d, the tag
> > "exists", even though the diff will be obviously empty.
>
> So, if a tag is successfully used one time, cvs assumes that
Dennis W. Bulgrien writes:
>
> Could one use:
> cvs rtag -r oldname newname .
No. That will create a revision tag pointing to the most recent
revision on the branch rather than creating a new name for the branch
itself. Likewise, adding a -b to create branch tag rather than a
revision tag will
I trying to setup a new CVS repository. I would like my various
modules to share the same src/ tree so I will not have a seperate
subdirectory for each project. Here's my first approach:
0. cvs -d $CVSROOT init
1. cd $home/project1
2. cvs import -m "Imported Source" . project1 start
This works
Hi,
How can I put a tag on most current sources in specific branch using rtag?
For main trunk I simply use rtag "tagname", but how to do it for a
specific branch?
I know I can do it locally using tag, bug I try to avoid using 'tag'
command because it is not stored in history.
The only solution I s
Maxio [mailto:[EMAIL PROTECTED] wrote:
> How can I put a tag on most current sources in specific
> branch using rtag?
> For main trunk I simply use rtag "tagname", but how to do it for a
> specific branch?
cvs rtag -r existing-branch-tag new-tag
should do it.
--
Jim Hyslop
Senior Software Desi
11 matches
Mail list logo