From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Eric Paris <eparis@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [git pull] aush^H^Hdit queue
Date: Tue, 17 Jan 2012 16:44:35 -0800 [thread overview]
Message-ID: <CA+55aFzkT+GAjd_-Ybb2MOHhfhqAe1+NR2NtXUfPS0Q_XqLOCg@mail.gmail.com> (raw)
In-Reply-To: <20120118003840.GT23916@ZenIV.linux.org.uk>
On Tue, Jan 17, 2012 at 4:38 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> Missed that one (and normally I do hunt for typos in commit messaged when
> applying). What do you prefer - fix on top of the branch or --amend to
> commit in question + cherry-pick of the rest on top of amended? Alternatively,
> that could be --amend'ed in the merge commit...
I'll fix it up in the merge.
Linus
next prev parent reply other threads:[~2012-01-18 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 21:34 [git pull] aush^H^Hdit queue Al Viro
2012-01-18 0:21 ` Linus Torvalds
2012-01-18 0:38 ` Al Viro
2012-01-18 0:44 ` Linus Torvalds [this message]
2012-01-18 0:45 ` Al Viro
2012-01-18 0:47 ` Al Viro
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=CA+55aFzkT+GAjd_-Ybb2MOHhfhqAe1+NR2NtXUfPS0Q_XqLOCg@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).