[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Verifymsg on branches?

From: Uwe Fritsch
Subject: Re: Verifymsg on branches?
Date: Mon, 20 Nov 2000 17:37:53 -0800


Thanks for your answer.

Instead of changing the entered log message after the user has entered
it, I rather would like to make the user aware that he has to enter a
Bug ID in the log message.

My idea was to have a different log template for the trunk as compared
to the branch. As this seems not possible, I now think it would be
enough to add the BugID line to the generic template and only do the
test whether the Bug ID was entered if the commit is done on the branch.

But if you can't check for a tag name at verifymsg this will also not
work, right? The only possibility would be to check for a "branch
version number", i.e. 4 digits instead of 2.

How do others enforce that Bug IDs are entered into the log message?


----- Original Message -----
From: "Laird Nelson" <address@hidden>
To: "Uwe Fritsch" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, November 14, 2000 7:03 AM
Subject: Re: Verifymsg on branches?

> Uwe Fritsch wrote:
> > we used the verifymsg mechanism in the past to check for some
> > for commit messages. As we create a branch for each release, we
> > like to add an additional keyword for bug numbers, but only if a new
> > version is committed to the branch.
> Well, you can't really do this (yes, you SHOULD be able to).  This is
> due to two major things:
> 1. You cannot get the new version number of a file being committed.
> you'll never know if that file is going onto a branch or not.  The
> you can do is guess based off the old number of the file.  This works
> for most cases, as most users aren't using the -r switch to cvs
> 2. You can't add anything to the message at commitinfo or verifymsg
> time.  The message being verified is read only.
> What you *could* do is do something really clever with loginfo.
> Basically, since loginfo gives you the old and new version numbers,
> could invoke cvs admin -m (haven't tried this; don't know if it's
> supported; rcs -m lets you replace one version's log message with
> another) if the new revision number contains more than one period in
> The other thing to do would be to apply your new keyword as a tag
> instead.
> Cheers,
> Laird
> --
> W: address@hidden / P: address@hidden
> Good, cheap, fast: pick two.
> _______________________________________________
> Info-cvs mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]