From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: linux-next: unusual update of the security tree
Date: Thu, 06 Dec 2012 15:56:41 -0800 [thread overview]
Message-ID: <50C130B9.4030207@schaufler-ca.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1212071020050.7590@tundra.namei.org>
On 12/6/2012 3:21 PM, James Morris wrote:
> On Thu, 6 Dec 2012, Linus Torvalds wrote:
>
>> Have people pulled that thing into anything else? Because quite
>> frankly, I think it's unsalvageable except with a rebase.
> AFAIK, only developers such as Casey will have pulled it for development
> purposes.
>
> And sorry, I should be checking the trees I pull from more carefully.
I have messed up and believe that I understand my error and the
impact that it has had on others. I also believe that I understand
what I should be doing henceforth. Once I get the word from James
I will rebase my tree from his. I will stop doing merges except as
recommended.
next prev parent reply other threads:[~2012-12-06 23:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 23:16 linux-next: unusual update of the security tree Stephen Rothwell
2012-11-27 23:28 ` Stephen Rothwell
2012-11-27 23:30 ` Linus Torvalds
2012-11-27 23:57 ` Stephen Rothwell
2012-11-27 23:45 ` Casey Schaufler
2012-11-28 0:01 ` Stephen Rothwell
[not found] ` <CA+55aFwdk9FiW4u_f-Dq6+jtuD9kY-zBqPpMVc2OHJFnzaAbzA@mail.gmail.com>
2012-12-03 15:26 ` James Morris
2012-12-06 13:25 ` James Morris
2012-12-06 16:25 ` Linus Torvalds
2012-12-06 21:27 ` Stephen Rothwell
2012-12-06 23:21 ` James Morris
2012-12-06 23:56 ` Casey Schaufler [this message]
2012-12-13 2:24 ` Stephen Rothwell
2012-12-14 3:11 ` James Morris
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=50C130B9.4030207@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.