From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: back merge of Linus' tree into the vfio tree
Date: Fri, 6 Sep 2013 09:08:26 +1000 [thread overview]
Message-ID: <20130906090826.947212e7d5383837bff881f5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
Hi Alex,
I noticed that you have back merged Linus' tree into yours. Linus
usually takes a dim view of that - especially when there is no
explanation in the merge commit message. i.e. you shouldn't to that
unless you really need to - and then you should explain why you did it.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-09-05 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 23:08 Stephen Rothwell [this message]
2013-09-05 23:14 ` linux-next: back merge of Linus' tree into the vfio tree Alex Williamson
2013-09-06 3:31 ` Stephen Rothwell
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=20130906090826.947212e7d5383837bff881f5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alex.williamson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 NNTP newsgroup(s).