Must be a pretty fundamental change to get the result Mark wants. Is there
any documentation for this patch? I'd like to apply it but I'd rather
appreciate what it does before applying it.
Andy
-Original Message-
From: Derek R. Price [mailto:[EMAIL PROTECTED]]
There's still a patch up
Andy Baker wrote:
Must be a pretty fundamental change to get the result Mark wants. Is there
any documentation for this patch? I'd like to apply it but I'd rather
appreciate what it does before applying it.
First, I just noticed that I posted the link to the wrong patch. The proper
link
Thanks Derek. I'll give that a go
Andy
-Original Message-
From: Derek R. Price [mailto:[EMAIL PROTECTED]]
http://alumni.engin.umich.edu/~oberon/ccvs.newfmtstrings.1-11.diff
NOTICE AND DISCLAIMER:
This email (including attachments) is confidential. If you have received
this
Ah. I see (next time I'll read the posting properly!). Good 'un that.
Nothing obvious springs to mind.
-Original Message-
From: Mark [mailto:[EMAIL PROTECTED]]
Since taginfo is in a sense, a pre-op trigger, the tag won't be
placed in the RCSfile until the taginfo script successfully
You could create a rule that says branches are all lowercase and
non-branch tags are all uppercase. Enforcement could be dictated
through a script you write that the users must use to lay tags...
donald
On Thu, Sep 14, 2000 at 08:50:04AM -0400, Laird Nelson wrote:
Is there any way to
Another taginfo question (maybe a bug report).
Cederqvist says that the taginfo script is supposed to get five
arguments: tag, action, directory, file and revision.
But when I do a cvs tag -d someTag someFile.txt I get three: tag
("someTag"), action ("del") and directory
Laird Nelson writes:
Cederqvist says that the taginfo script is supposed to get five
arguments: tag, action, directory, file and revision.
No it doesn't, it says that the taginfo script gets tag, action, and
directory, and that any additional arguments are file/revisions pairs.
The taginfo
