From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>
Cc: Venkataramanan Kumar <venkataramanan.kumar@linaro.org>,
<libc-ports@sourceware.org>, Patch Tracking <patch@linaro.org>
Subject: Re: [PATCH] AArch64 - Add parameter to __mount routine
Date: Tue, 24 Sep 2013 16:03:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1309241602200.31872@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFqB+Pxo91d_v4owORzu7EM3v92vyWRwQOz6c2U5ov7H7Yx-wQ@mail.gmail.com>
On Tue, 24 Sep 2013, Marcus Shawcroft wrote:
> Venkat, I've committed your patch.
Please remember when committing patches for someone else to use git commit
--author="Name <email>" so the patch's author is correctly recorded in the
git logs.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2013-09-24 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 12:45 Venkataramanan Kumar
2013-09-16 11:31 ` Marcus Shawcroft
2013-09-16 13:35 ` Venkataramanan Kumar
2013-09-24 12:19 ` Marcus Shawcroft
2013-09-24 16:03 ` Joseph S. Myers [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=Pine.LNX.4.64.1309241602200.31872@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=marcus.shawcroft@gmail.com \
--cc=patch@linaro.org \
--cc=venkataramanan.kumar@linaro.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).