From: Stephen Rothwell <sfr@canb.auug.org.au>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Containers <containers@lists.linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] namespace updates for v3.17-rc1
Date: Wed, 6 Aug 2014 16:06:08 +1000 [thread overview]
Message-ID: <20140806160608.218b6944@canb.auug.org.au> (raw)
In-Reply-To: <87lhr2tcyx.fsf@x220.int.ebiederm.org>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
Hi Eric,
On Tue, 05 Aug 2014 22:16:06 -0700 ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> I am not certain what your point is.
I am just trying to give Linus a heads up for branches that have not
had much exposure before he is asked to pull them.
> There have been no commits added since the merge window opened.
>
> There was one commit changed to fix a typo. I documented that already.
Yes, that is what confused my, sorry, since that commit and the ones
following are new commits but unchanged patches.
> There were some commits pushed to the tree as late as friday that had
> been out for review earlier than that and it is possible that you did
> not pick them up in linux-next until monday. That doesn't mean I added
> anything after the merge window opened.
Correct.
> I have also made certain all of these commits have at least had a chance
> to show up in linux-next.
>
> As for missing cool tags shrug. The people looking at my code didn't
> feel like saying the magic words so I didn't include cool tags.
Maybe you should push them ... these tags are not just "cool", they
give less involved people some indications of what has happened in the
life of a patch.
> Beyond that I have been quite out of it recently and this is what I had
> time to do. If I had had a little more time and energy I would have
> included unmount on unlink patches that still need magic to happen to
> keep from blowing the stack in pathological cases on everything except
> x86_64. That code has been sitting in linux-next.
>
> Which is a my long winded way of say it sounds like you are accusing me
> of being irresponsible, and my way of saying that I have tested and
I did not mean to accuse, there are reasons (as you have pointed out)
that things get added late, or rewritten.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-06 6:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 0:57 Eric W. Biederman
2014-08-06 4:46 ` Stephen Rothwell
2014-08-06 5:16 ` Eric W. Biederman
2014-08-06 6:06 ` Stephen Rothwell [this message]
2014-08-06 6:30 ` Eric W. Biederman
2014-08-07 13:28 ` Theodore Ts'o
2014-08-13 2:46 ` Andy Lutomirski
2014-08-13 4:17 ` Eric W. Biederman
2014-08-13 4:38 ` Andy Lutomirski
[not found] ` <CAOP=4widH1rMZ1O=hzAT+M_8exdzRPA8pJ+wH29AQ9L0ogu9nw@mail.gmail.com>
2014-08-13 10:24 ` Eric W. Biederman
2014-08-13 17:03 ` Andy Lutomirski
2014-08-14 0:03 ` [PATCH] fs: Remove implicit nodev for new mounts in non-root userns Andy Lutomirski
2014-08-15 19:05 ` Serge Hallyn
2014-08-15 19:16 ` Andy Lutomirski
2014-08-15 19:37 ` Serge Hallyn
2014-08-15 19:56 ` Andy Lutomirski
2014-08-15 20:16 ` Serge Hallyn
2014-08-15 20:16 ` Serge Hallyn
2014-08-28 1:35 ` Andy Lutomirski
2014-08-15 18:41 ` [GIT PULL] namespace updates for v3.17-rc1 Andy Lutomirski
2014-08-20 15:06 ` Richard Weinberger
2014-08-21 4:53 ` Eric W. Biederman
2014-08-21 6:29 ` Richard Weinberger
2014-08-21 7:24 ` Richard Weinberger
2014-08-21 13:54 ` Eric W. Biederman
2014-08-21 13:12 ` Christoph Hellwig
2014-08-21 13:22 ` Richard Weinberger
2014-08-21 14:09 ` Eric W. Biederman
2014-09-03 21:18 ` Richard Weinberger
2014-11-25 23:15 ` Richard Weinberger
2014-11-29 16:58 ` Richard Weinberger
2014-08-21 13:43 ` Eric W. Biederman
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=20140806160608.218b6944@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®