| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kekalainen, Otto" <ottoke(at)amazon(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Fix various spelling errors |
| Date: | 2022-03-15 16:46:34 |
| Message-ID: | 328924.1647362794@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kekalainen, Otto" <ottoke(at)amazon(dot)com> writes:
> Please next time use `git am` to import the patch so that author and other
> commit metadata is kept, or if you apply patches manually then commit with `git
> --author` so that original author will be correct in the commit and your name
> will be only in the committer field.
This is not our practice. We credit authors in the body of the commit
message, but we don't worry about the git metadata. git is a tool we
happen to be using at the moment, but it doesn't run the project,
and in any case it's far short of being adequate for such a purpose.
What would you do with multiple-author patches, for a start?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-03-15 16:47:22 | Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints |
| Previous Message | Robert Haas | 2022-03-15 16:44:49 | Re: Corruption during WAL replay |