Re: antisocial things you can do in git (but not CVS) - Mailing list pgsql-hackers

From Dave Page
Subject Re: antisocial things you can do in git (but not CVS)
Date
Msg-id AANLkTimcWwPm7J9WGp1H_KcUlC3TZQhndBirFprjxiLb@mail.gmail.com
Whole thread Raw
In response to Re: antisocial things you can do in git (but not CVS)  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: antisocial things you can do in git (but not CVS)
List pgsql-hackers
On Tue, Jul 20, 2010 at 8:12 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> My preference would be to stick to a style where we identify the
>> committer using the author tag and note the patch author, reviewers,
>> whether the committer made changes, etc. in the commit message.  A
>> single author field doesn't feel like enough for our workflow, and
>> having a mix of authors and committers in the author field seems like
>> a mess.
>
> Well, I had looked forward to actually putting the real author into the
> author field.

I hadn't realised that was possible until Guillaume did so on his
first commit to the new pgAdmin GIT repo. It seems to work nicely:

http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=08e2826d90129bd4e4b3b7462bab682dd6a703e4

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Synchronous replication
Next
From: Markus Wanner
Date:
Subject: Re: dynamically allocating chunks from shared memory