From: Sverre Rabbelier <srabbelier@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC PATCH 1/2] SubmittingPatches: Add new section about what to base work on
Date: Sun, 18 Apr 2010 22:24:07 +0200 [thread overview]
Message-ID: <j2yfabb9a1e1004181324w759d6dcbs8a68a402b3b91a78@mail.gmail.com> (raw)
In-Reply-To: <1271620400-sup-4850@kytes>
Heya,
On Sun, Apr 18, 2010 at 21:54, Ramkumar Ramachandra <artagnon@gmail.com> wrote:
> From: Junio C Hamano <gitster@pobox.com>
That's my fault, I should have been more clear in that this should
have been at the top of the message :). Either way, the idea (that
this patch was a literal re-send of Junio's patch) was conveyed
successfully I think.
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2010-04-18 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 19:54 [RFC PATCH 1/2] SubmittingPatches: Add new section about what to base work on Ramkumar Ramachandra
2010-04-18 20:24 ` Sverre Rabbelier [this message]
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=j2yfabb9a1e1004181324w759d6dcbs8a68a402b3b91a78@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).