Re: git: uh-oh - Mailing list pgsql-hackers

From Michael Haggerty
Subject Re: git: uh-oh
Date
Msg-id 4C845906.102@alum.mit.edu
Whole thread Raw
In response to Re: git: uh-oh  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: git: uh-oh  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Max Bowsher <maxb@f2s.com> writes:
>> For both, see http://github.com/maxb
> 
> [...] The only real gripe I can find to make is that in the cases where
> a file is added to a back branch, the "manufactured" commit is
> invariably blamed on committer "pgsql".  Can't we arrange to blame it
> on the person who actually added the file?  (I wonder whether this is
> related to the fact that the same commits have made-up timestamps,
> which we already griped about.)

CVS does not record when a branch was created or by whom.  If a git
commit has to be created for such events, cvs2git attributes them to a
configurable username, which Max has set to be "pgsql".  It chooses the
latest possible timestamp that is consistent with other (timestamped)
changesets that depend on it.

Does cvs2cl do something better?  If so, how?

Michael


pgsql-hackers by date:

Previous
From: Andrew Chernow
Date:
Subject: Re: returning multiple result sets from a stored procedure
Next
From: Tom Lane
Date:
Subject: Re: git: uh-oh