All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Sage Weil <sweil@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [GIT PULL] Ceph updates for 4.7-rc1
Date: Thu, 26 May 2016 14:18:37 -0700	[thread overview]
Message-ID: <CA+55aFxZRUn333pP3fNN9NDLxp_JiZu+=vJH=k6gohQtDQRA5Q@mail.gmail.com> (raw)
In-Reply-To: <20160526201011.GM14480@ZenIV.linux.org.uk>

On Thu, May 26, 2016 at 1:10 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> How about the things like followups to earlier merges?

Small and obvious follow-ups are fine. What I really hated about this
ceph pull request was that it was multiple thousand lines of changes,
with no previous work or warning, and effectively no time in
linux-next.

Your for-linus branch is three small commits that actually restore old
functionality (well, one of them is documentetion) that got removed by
the big stuff you sent early (*).

So not at all the same kind of thing, and not problematic at all.

              Linus

(*) thanks, btw - you used to be one of the late people, now lately
you've been one of the early ones.

  reply	other threads:[~2016-05-26 21:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-26 18:18 [GIT PULL] Ceph updates for 4.7-rc1 Sage Weil
2016-05-26 18:31 ` Linus Torvalds
2016-05-26 19:02   ` Sage Weil
2016-05-26 19:54     ` Linus Torvalds
2016-05-26 20:10       ` Al Viro
2016-05-26 21:18         ` Linus Torvalds [this message]
2016-05-26 21:13   ` Linus Torvalds
2016-05-26 21:46     ` Sage Weil
2016-05-27  2:16       ` Linus Torvalds
2016-06-10 20:42 ` Arnd Bergmann
2016-06-10 21:32   ` Linus Torvalds
2016-06-10 23:04     ` Arnd Bergmann
2016-06-11 22:50     ` Arnd Bergmann
2016-06-13 13:06     ` Arnd Bergmann

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+55aFxZRUn333pP3fNN9NDLxp_JiZu+=vJH=k6gohQtDQRA5Q@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sweil@redhat.com \
    --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 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.