Hi!
Anyone knows if there is a CVS command that can be used to see which
files (and their version) that has been tagged with a specific tag?
If I do cvs status -v I get a lot of info on every file, including
*all* tags. I guess I could write a script that extracs file name with
tag, using
sources - cvs -q up -dP
tag the repository - cvs tag rel_1-20040630
I go into the rel_2/testproj sandbox and issue the following commands:
make sure i have the latest srouces - cvs -q up -dP
tag the repository - cvs tag rel_2-20040630
Now I'm ready to merge. Since I want to merge from
[EMAIL PROTECTED] wrote:
Anyone knows if there is a CVS command that can be used to
see which files (and their version) that has been tagged with
a specific tag?
cvs -nq up -r tag-you-are-interested-in
--
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc.
Khyati Nayak wrote:
I have tags assigned to some of my files in the repository to
mark them for something different. Now if one of these files
is updated and committed, how do I get the tag on the latest
version? Or get rid of it from the old and add it to new?
Use the -F option.
--
Jim
sure i have the latest sources - cvs -q up -dP
tag the repository - cvs tag rel_1-20040630 I go into the rel_2/testproj
sandbox and issue the following commands: make sure i have the latest srouces
- cvs -q up -dP
tag the repository - cvs tag rel_2-20040630 Now I'm ready to merge. Since I
[EMAIL PROTECTED] (John Hanny) writes:
I'd like a cvs command that tells me what files in the current
directory are new. One hack that I've been using is cvs update. The
files that are prefixed by '?' are new. Unfortunately, this has the
side-effect of updating my local directory files if
Jim.Hyslop [EMAIL PROTECTED] writes:
work wrote:
[...]
At this point, I'm not overly concerned about deleted or added files
(to me they are much easier to deal with since the entire file is
involved).
You will have to use 'cvs add' and 'cvs remove' to have these files added or
removed
Jim.Hyslop writes [re merging]:
You will have to use 'cvs add' and 'cvs remove' to have these files added or
removed from the trunk.
Not so -- a merge with two -j options should handle that automatically.
-Larry Jones
What a stupid world. -- Calvin
Sergei Organov wrote:
Jim.Hyslop [EMAIL PROTECTED] writes:
You will have to use 'cvs add' and 'cvs remove' to have these files
added or removed from the trunk.
I don't think he will. At least for me it works
automatically. I mean all the files are already added/removed
after the
[ On Monday, June 28, 2004 at 19:02:19 (-0700), Paul Sander wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
I have never, ever advocated changing the format of an RCS file in a
way that would break the ci, co, rcs, or rlog programs. And although
I strongly advocate
Whenever a module is checked in, the username is whoever did the commit. I
want the user to always be cvs:cvs. I know there is a way to do this --
something in the passwd file I think -- but I cannot find it in the manual.
I use cvs 1.11.1p1 witjh both :pserver: and :ext: connections
--
[ On Tuesday, June 29, 2004 at 02:18:26 (-0700), Paul Sander wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
I.e. How do you propose to make it possible for the standard RCS tools
alone to re-create _every_ revision from all files created by this
hacked system?
[ On Monday, June 28, 2004 at 14:58:03 (-0700), Mark D. Baushke wrote: ]
Subject: Re: Smoke, FUD (was Re: CVS corrupts binary files ...)
Yes, but diff is not diff3. diff is used for the
delta format. diff3 is used by rcsmerge, not for
fundamental version deltas.
I think you're confused --
[ On Monday, June 21, 2004 at 17:50:49 (-0500), Ababccc wrote: ]
Subject: Project in a cvs, library in another
I'm wondering what people usually do, in case there is a project on CVS
which uses a C++ library which is in a completely separated CVS.
If the library gets changed (for its own
[ On Tuesday, June 29, 2004 at 19:34:25 (-0700), Paul Sander wrote: ]
Subject: RE: CVS corrupts binary files ...
When you speak about how great NASA is and mention the antiquity of some
of their processes, remember that the paper checklists have since
contributed to the failure of several
I want to play with the diff patch tools a bit myself just to see
if I could see something go wrong with CVS and binary files if those
files were run through something that would binhex them (similar to
uuencoding) via a CVS wrapper.
Everything seemed to work as I expected.
If I understand
When I use a client which inserts the global '-l' option together with
my newly upgraded server, I get the expected global `-l' option
ignored warning.
However, if I also specify a compression level, I get the following:
[EMAIL PROTECTED] tools] cvs -nq -z1 up
cvs update: inflate: unknown
17 matches
Mail list logo
