Tay Ray Chuan <rctay89@xxxxxxxxx> writes:
> On Sat, Jun 6, 2009 at 4:54 AM, Jakub Narebski<jnareb@xxxxxxxxx> wrote:
>>> From: Mike Hommey <mh@xxxxxxxxxxxx>
>>> Subject: [WIP Patch 09/12] Use the new http API in fetch_symref()
>>
>> What is the subject of this patch:
>> "http-push.c::fetch_symref(): use the new http API"
>> or
>> "Use the new http API in fetch_symref()"
>> [...]
>> If you wanted to note old subject, it would be better to put it in
>> comments (here).
>
> Since the title of the patch differed from Mike's original, I was
> afraid the attribution to the author's original patch was lost on the
> reader of the commit message, thus I added the original subject, in
> addition to the author and date, into the commit message.
Please don't.
If you chose to use a better (in your opinion) subject from the original
one, we'd want to have that improved one in our commit. The same thing if
you chose to rewrite the proposed commit log message, or the contents of
the patch, to add your own improvement. That is what we review here, and
if people think your submitted version is good, that is what we want to
record as a commit.
So, in general we would want to see something like this:
(1) From: Tay Ray Chuan <rctay89@xxxxxxxxx>
Subject: [PATCH 19/23] http-push.c:fetch_symref(): use the new HTTP API
(2) From: Mike Hommey <mh@xxxxxxxxxxxx>
(3) Now the contents of a file can be slurped into a strbuf with a single
call to http_get_strbuf(), use it to simplify fetch_symref().
(4) Signed-off-by: Mike Hommey <mh@xxxxxxxxxxxx>
Signed-off-by: Tay Ray Chuan <rctay89@xxxxxxxxx>
(5) ---
(6) This is based on Mike's earlier patch:
Subject: [WIP Patch 09/12] Use the new http API in fetch_symref()
Date: Sun, 18 Jan 2009 09:04:34 +0100
I retitlted Mike's patch in order to ...
Also changed frotz and nitfol so that they distim doshes better...
(7) http-push.c | 20 +++-----------------
1 files changed, 3 insertions(+), 17 deletions(-)
(8) diff --git a/http-push.c b/http-push.c
...
That is,
(1) RFC2822 headers your MUA gives us;
(2) In-body (fake)headers for From: if the author is different from
what (1) records. If you are forwarding somebody else's patch
verbatim without modification, you may want to add Date: to keep
the original datestamp, but if you are sending a version with your
own improvements, we would rather use the Date: recorded in (1) in
the final commit.
(3) Proposed commit log message;
(4) Chain of Signed-off-by lines;
(5) Three-dash separator;
(6) Commentary to explain the history of the patch, and/or background
information if necessary,
(7) diffstat;
(8) the patch itself.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html