ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] "depth" of the tree of maintainers
Date: Fri, 02 May 2014 22:04:08 +0200	[thread overview]
Message-ID: <1399061048.7206.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1405022121070.29834@pobox.suse.cz>

On Fri, 2014-05-02 at 21:42 +0200, Jiri Kosina wrote:
> Is our tree too flat? This might turn into just a question to Linus than 
> really a discussion topic.
>
> It seems to me (and it has been the case for a few past years, so it's 
> probably not an issue at the end of the day) like there are many places 
> where we are violating a natural tree-like hierarchy our development model 
> has, with many people sending pull requests directly to Linus instead of 
> going through sub-maintainers. Is this really a problem? If so, how to 
> deal with it?

I don't know about that, but I'm pretty far removed and have been
wondering if it's too *deep*, since a pull request from me to John to
DaveM to Linus can take a very long time to actually get into the
tree ...

This gets to the point where sometimes shortly before the merge window
opens I don't even bother sending fixes to the current tree any more but
just put them into the -next branch marked Cc stable, which has Greg
(rightfully) complaining that there shouldn't be so much stable material
coming into the tree in the merge window since presumably most of that
wasn't actually *developed* in that time)

johannes

  reply	other threads:[~2014-05-02 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 19:42 Jiri Kosina
2014-05-02 20:04 ` Johannes Berg [this message]
2014-05-02 20:33 ` John W. Linville

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=1399061048.7206.2.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jkosina@suse.cz \
    --cc=ksummit-discuss@lists.linuxfoundation.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