From: Junio C Hamano <gitster@pobox.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Mike Hommey <mh@glandium.org>
Subject: Re: [PATCH 19/23] http-push.c::fetch_symref(): use the new http API
Date: Fri, 05 Jun 2009 22:32:28 -0700 [thread overview]
Message-ID: <7vvdnadj0z.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <be6fef0d0906051802n4f6d5df3g453b292787ed62d0@mail.gmail.com> (Tay Ray Chuan's message of "Sat\, 6 Jun 2009 09\:02\:32 +0800")
Tay Ray Chuan <rctay89@gmail.com> writes:
> On Sat, Jun 6, 2009 at 4:54 AM, Jakub Narebski<jnareb@gmail.com> wrote:
>>> From: Mike Hommey <mh@glandium.org>
>>> 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@gmail.com>
Subject: [PATCH 19/23] http-push.c:fetch_symref(): use the new HTTP API
(2) From: Mike Hommey <mh@glandium.org>
(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@glandium.org>
Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
(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.
next prev parent reply other threads:[~2009-06-06 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 16:05 [PATCH 19/23] http-push.c::fetch_symref(): use the new http API Tay Ray Chuan
2009-06-05 20:54 ` Jakub Narebski
2009-06-06 1:02 ` Tay Ray Chuan
2009-06-06 5:32 ` Junio C Hamano [this message]
2009-06-06 7:20 ` Tay Ray Chuan
[not found] <cover.1244277116.git.rctay89@gmail.com>
2009-06-06 8:43 ` Tay Ray Chuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vvdnadj0z.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=mh@glandium.org \
--cc=rctay89@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).