As promised, a diff to the manual.
This is a context (-c) diff on the 1.11.14 version of the file. Please let me know if
that's not okay.
*** cvs.texinfo Wed Feb 4 19:05:46 2004
--- /home/apj/cvs.texinfo Tue Mar 30 11:02:33 2004
***
*** 3570,3576
One potentially
Andy Jones [EMAIL PROTECTED] writes:
As promised, a diff to the manual.
This is a context (-c) diff on the 1.11.14 version of the file. Please let
me know if that's not okay.
[...]
+ This will work for locally modified files, but not
+ for locally deleted ones.
Did you check it
Andy Jones [EMAIL PROTECTED] writes:
Did you check it doesn't work for locally removed files (for which cvs
remove has been executed)? If it does, the description needs further
cleanup, I think.
What about locally removed directories?
In both cases cvs tag warns or errors, then bombs out,
Did you check it doesn't work for locally removed files (for which cvs
remove has been executed)? If it does, the description needs further cleanup,
I think.
What about locally removed directories?
In both cases cvs tag warns or errors, then bombs out, regardless of whether the -c
tag has been
On a different note: IIRC you mentioned earlier that these deleted files are
not part of the release, but you don't want to remove them from the
repository. What harm would there be if those files actually had the tag
applied?
Not much, admittedly. The point is that they don't compile, and I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Jones wrote:
While doing some further testing I have discovered that cvs tag -c
ignores removed files.
That is, you can remove a file from the sandbox with rm and then do a
cvs tag -c, and the removed file will be tagged with no warning or
Jason Carucci
No, I believe cvs will tag the files in the repository, the files in your
working directory are irrelevant for this operation.
I'm not saying that CVS behaved wrongly, just in a way that was counterintuitive. To
say that cvs tag requires a working directory, but not the files in
Patches thoughtfuly considered. :)
Well, hell. I'd be honoured. It's not as if it would take more than a couple of
lines.
Do you literally mean a patch-compatible diff to some version of the current
Cederqvist? If so, which version?
___
]
Subject: Re: cvs tag: some slightly counterintuitive behaviour
Jason Carucci
No, I believe cvs will tag the files in the repository, the files in
your working directory are irrelevant for this operation.
I'm not saying that CVS behaved wrongly, just in a way that
was counterintuitive. To say
Why can't you just choose the files you want to tag and run the TAG
command only on those. This way only those files get tagged and not the
complete module, which is not want you as it is want to happen.
Because I have 12,766 files, and I want to tag all but about 30 of them. Working out
which
Andy Jones wrote:
Why can't you just choose the files you want to tag and run the TAG
command only on those. This way only those files get tagged and not the
complete module, which is not want you as it is want to happen.
Because I have 12,766 files, and I want to tag all but about 30 of
Andy Jones [EMAIL PROTECTED] writes:
Jason Carucci
[...]
Derek Price
The work-around, and a pretty straight-forward one I should think, is to
commit your changes before tagging.
No, no. I don't want to remove the files. I just want to not tag them. Now
it looks like I will have to tag the
Andy Jones [EMAIL PROTECTED] writes:
Why can't you just choose the files you want to tag and run the TAG command
only on those. This way only those files get tagged and not the complete
module, which is not want you as it is want to happen.
Because I have 12,766 files, and I want to tag all
Andy Jones writes [in very long lines]:
No, no. I don't want to remove the files. I just want to not tag
them. Now it looks like I will have to tag the whole sandbox and then
untag a list of about 30 files - not fun.
cvs tag foo *
-Larry Jones
If I get a bad grade, it'll be YOUR
Andy Jones wrote:
Because I have 12,766 files, and I want to tag all but about
30 of them. Working out which 30 is a long and laborious
process of checking by hand.
cvs -nq update
should show you a list of files that need to be updated. If you are
following good VM practises, the only
-Original Message-
From: Andy Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, 26 March, 2004 16:01 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: cvs tag: some slightly counterintuitive behaviour
Why can't you just choose the files you want to tag and run the TAG
command only on those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Jones wrote:
Now I come to make a release tag. My expectation is that since cvs tag
requires a working directory then it will operate on that working
directory, tagging the files in it but *not* the files I have removed.
`cvs tag' is defined
No, I believe cvs will tag the files in the repository, the files in your
working directory are irrelevant for this operation.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Andy Jones
Sent: Thursday, March 25, 2004 11:52 AM
To: [EMAIL PROTECTED]
Andy Jones wrote:
I've found some behaviour of cvs tag that breaks the principal of least astonishment
- at least, for me.
In short: cvs tag doesn't tag the files in the working directory, it tags the files
it thinks are there.
I'm preparing a release. Some of the code is
Andy Jones wrote:
I'm preparing a release. Some of the code is questionable -
I don't know if it is dead or not but it certainly does not
want to be part of the release. So I've been deleting these
files from the working directory.
Now I come to make a release tag.
At this point, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop wrote:
Any thoughts? I think that at the very least this behaviour
should be spelled out more clearly in the manual.
That I would go along with.
Patches thoughtfuly considered. :)
Derek
- --
*8^)
Email: [EMAIL
21 matches
Mail list logo
