[Top][All Lists]

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

Re: capturing all aspects of a commit

From: Mark D. Baushke
Subject: Re: capturing all aspects of a commit
Date: Sun, 25 May 2003 07:39:24 -0700

Akos Maroy <address@hidden> writes:

> Max Bowsher wrote:
> > There was an experimental patch posted a while ago:
> >
> thanks. in that post, it says that it's an experimental patch, mainly
> to gather feedback. has there been any feedback? will this feature be
> included in the production version of CVS anytime soon?
> Akos

I have not seen any feedback on that patch. If you want to use it, feel
free to do so and give the author (Corey Minyard) such feedback. I would
guess that most folks may have only replied to the author of the patch
rather than the list.

This feature will not be included in the production version of CVS
anytime soon as the author was fairly explicit that the feature was not
yet ready for production use and did not include any tests for
in the patch. If/when other folks think that such a patch is a useful
one for consideration in the baseline CVS version, it should be
discussed a first to see if it is a desirable direction for CVS to go.

All that said, there is nothing inherently impossible for you to create
some kind of a commitid database as a part of the commitinfo or
verifymsg trigger processing (possibly based on the time-of-day and the
branch and the userid doing the commit) and have that information used
by the loginfo script to record the module, file and version information
of each file associated with the commit.

        -- Mark

reply via email to

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