[Top][All Lists]

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

Re: capturing all aspects of a commit

From: Akos Maroy
Subject: Re: capturing all aspects of a commit
Date: Sun, 25 May 2003 16:51:45 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314

Mark D. Baushke wrote:
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.

I see. thanks for the info.

in the patch. If/when other folks think that such a patch is a useful

if there is a place to vote, put my YES into the vote box :)

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.

frankly, I don't see how that could be done. as I wrote earlier, for each directory of the same commit, the loginfo is called seperately, with a different timestamp. thus one can only use heuristics to determine what might be a single commit.


reply via email to

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