public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Huang Shijie <b32955@freescale.com>,
	linux-mtd@lists.infradead.org,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org
Subject: Re: No pull for mtd?
Date: Tue, 30 Jul 2013 13:50:31 +0300	[thread overview]
Message-ID: <1375181431.14869.113.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAN8TOE_y=mDY4frFB9kmedhGnNhf4pQwqH1q+fAcDAE_RNwO+A@mail.gmail.com>

On Thu, 2013-07-18 at 22:33 -0700, Brian Norris wrote:
> > Normally though, I use Artem's l2-mtd tree a bit like patchwork. He
> > hoovers up most things from the list and even does some preliminary
> > fixes on them — so it's *much* more convenient for me than raw
> patchwork
> > would be. And it's close *enough* to what I'm actually going to
> accept,
> > that it's reasonable for it to be in linux-next as it is.
> 
> I guess I didn't fully grasp the relation between you and Artem. It
> seemed to me like Artem's tree was practically the pull request tree,
> that his status as "not the maintainer" simply gave him the luxury to
> rebase more freely, and that your sign-off (or sometimes pull request
> w/o adding sign-offs) was mostly just a rubber stamp.

Well, something like this. Depending on the load, David either sends my
tree to Linus almost intact, or goes through it patch-by-patch and does
real review: amends some, rejects some, etc.

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2013-07-30 10:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 12:47 No pull for mtd? Ezequiel Garcia
2013-07-16  2:58 ` Brian Norris
2013-07-17  7:44   ` Huang Shijie
     [not found]     ` <CAF4G-tLsOO_F-Mhn=+5vS2kkJuoeLJwrTdCR90DVuQQ+xn40aw@mail.gmail.com>
2013-07-17 23:02       ` Brian Norris
2013-07-17 23:13         ` David Woodhouse
2013-07-17 23:26           ` Brian Norris
2013-07-18  1:03             ` David Woodhouse
2013-07-19  5:33               ` Brian Norris
2013-07-20 12:22                 ` Huang Shijie
2013-07-30 11:04                   ` Artem Bityutskiy
2013-07-31  1:53                     ` Huang Shijie
2013-07-30 14:03                       ` Artem Bityutskiy
2013-07-30 15:26                         ` Artem Bityutskiy
2013-07-30 21:00                           ` Brian Norris
2013-07-31  2:24                         ` Huang Shijie
2013-07-30 20:45                           ` Brian Norris
2013-07-30 20:33                       ` Brian Norris
2013-07-30 10:50                 ` Artem Bityutskiy [this message]
2013-07-30 10:46               ` Artem Bityutskiy

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=1375181431.14869.113.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=linux-mtd@lists.infradead.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