RE: Taginfo question
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 at http://alumni.engin.umich.edu/~oberon/ccvs.tmpltfilter.final.diff that provides this functionality in addition to attempting to standardize the *info interfaces. It's fairly complete and works well, but I wanted some more opinions before updating the main tree. I have since reached the conclusion that the better direction is the XML pipe interface I brought up recently on bug-cvs but I haven't received any comments. Some of the XML pipe code has been implemented but not nearly enough to make it generally useful yet. Derek NOTICE AND DISCLAIMER: This email (including attachments) is confidential. If you have received this email in error please notify the sender immediately and delete this email from your system without copying or disseminating it or placing any reliance upon its contents. We cannot accept liability for any breaches of confidence arising through use of email. Any opinions expressed in this email (including attachments) are those of the author and do not necessarily reflect our opinions. We will not accept responsibility for any commitments made by our employees outside the scope of our business. We do not warrant the accuracy or completeness of such information. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Taginfo question
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 was: http://alumni.engin.umich.edu/~oberon/ccvs.newfmtstrings.1-11.diff The first link I posted was to another patch that provides functionality on top of this one and doesn't do everything it should, so I'd leave it alone unless you really want the additional functionality as it stands or feel like dooing some hacking. Anyhow, there isn't much external documentation. You can review my previous posts - here's the results of searches for ccvs.newfmtstrings.1-11.diff on the bug-cvs and info-cvs archive on mail-archive.com: http://www.mail-archive.com/bug-cvs@gnu.org/msg00598.html http://www.mail-archive.com/info-cvs@gnu.org/msg07456.html http://www.mail-archive.com/info-cvs@gnu.org/msg06744.html http://www.mail-archive.com/info-cvs@gnu.org/msg05603.html Use those if you want abstract descriptions. Be sure to follow the threads. The best thing to do is probably review the portions of the patch which affect doc/cvs.texinfo and maybe the individual ChangeLogs in the patch file itself if you want itemized functionality descriptions. Hope that's useful. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net ) -- I have sworn upon the alter of God eternal hostility against every form of tyranny over the mind of man. - Thomas Jefferson ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Taginfo question
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 email in error please notify the sender immediately and delete this email from your system without copying or disseminating it or placing any reliance upon its contents. We cannot accept liability for any breaches of confidence arising through use of email. Any opinions expressed in this email (including attachments) are those of the author and do not necessarily reflect our opinions. We will not accept responsibility for any commitments made by our employees outside the scope of our business. We do not warrant the accuracy or completeness of such information. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Taginfo question
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 exists. But the rlog command will, of course, work in helping to identify existing tags. NOTICE AND DISCLAIMER: This email (including attachments) is confidential. If you have received this email in error please notify the sender immediately and delete this email from your system without copying or disseminating it or placing any reliance upon its contents. We cannot accept liability for any breaches of confidence arising through use of email. Any opinions expressed in this email (including attachments) are those of the author and do not necessarily reflect our opinions. We will not accept responsibility for any commitments made by our employees outside the scope of our business. We do not warrant the accuracy or completeness of such information. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Taginfo question
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 determine from within a taginfo script whether the tag being added is a branch tag? I'm inclined to say no--no such information exists in any of the arguments etc. passed to taginfo, in the ,v file or in the environment. Cheers, Laird
Re: Taginfo question
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 ("wherever/someFile/lives").
Is this a bug?
Cheers,
Laird
Re: Taginfo question
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 script only gets called once per directory with all of the
affected files listed. If no files are affected, then there are no
additional arguments.
But when I do a cvs tag -d someTag someFile.txt I get three: tag
("someTag"), action ("del") and directory ("wherever/someFile/lives").
Is this a bug?
No, it means that the file didn't contain the tag, so there was nothing
to delete.
-Larry Jones
My brain is trying to kill me. -- Calvin
