From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: rebase of the drivers-x86 tree
Date: Mon, 15 Jul 2013 20:17:08 +0100 [thread overview]
Message-ID: <20130715191708.GA514@srcf.ucam.org> (raw)
In-Reply-To: <20130715101306.6d6fc3cb42ce956130606ac2@canb.auug.org.au>
On Mon, Jul 15, 2013 at 10:13:06AM +1000, Stephen Rothwell wrote:
> That is hardly a reason to rebase your tree. Just add another commit to
> correct the situation. The tree as it stood would not have affected
> anyone's building, running or bisecting.
I verified that the only difference before and after rebasing was that
the file permission was back the way it should be. Why clutter history?
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2013-07-15 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 0:04 linux-next: rebase of the drivers-x86 tree Stephen Rothwell
[not found] ` <f7e5023f-0e7e-4da1-a91d-5b9f4fd0db21@email.android.com>
2013-07-15 0:13 ` Stephen Rothwell
2013-07-15 19:17 ` Matthew Garrett [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=20130715191708.GA514@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).