linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, davem@davemloft.net
Subject: Re: Revised wireless tree management practices
Date: Mon, 14 Dec 2009 15:59:29 +0100	[thread overview]
Message-ID: <200912141559.29282.bzolnier@gmail.com> (raw)
In-Reply-To: <20091214142602.GC18945@tuxdriver.com>

On Monday 14 December 2009 03:26:02 pm John W. Linville wrote:
> On Mon, Dec 14, 2009 at 03:16:12PM +0100, Bartlomiej Zolnierkiewicz wrote:
> 
> > Now if only somebody could come up with a way to split 'monstermerges'
> > for Linus tree into something more fine-grained (thousands of commits in
> > a single merge is too much for anyone not directly involved into current
> > networking developments IMHO) I would be completely satisfied. ;)
> 
> You'll have to talk to Dave about that one, although FWIW I'm not

Yep, it was directed at him (since he was on cc: already).

> sure how to prevent that with the current "merge window" policy...

Hmmm, there are multiple ideas to investigate even within the current
"merge window" policy.  Decoupling driver trees from core changes should
certainly be possible (it works just fine in the storage area), some
architectures make heavy use of topic branches to prevent 'monstermerge'
issue etc.

Anyway this is just some food for thought for Dave once he finds some
time away from his usual more high-priority activities.. ;)

--
Bartlomiej Zolnierkiewicz

  reply	other threads:[~2009-12-14 15:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 21:10 Revised wireless tree management practices John W. Linville
2009-12-10  0:51 ` David Miller
2009-12-10 13:38 ` Kalle Valo
2009-12-10 13:47   ` John W. Linville
2009-12-10 14:04     ` Kalle Valo
2009-12-10 14:31       ` Luis R. Rodriguez
2009-12-10 14:37         ` John W. Linville
2009-12-10 14:53           ` Luis R. Rodriguez
2009-12-10 15:03             ` John W. Linville
2009-12-10 16:14               ` Luis R. Rodriguez
2009-12-10 16:25                 ` John W. Linville
2009-12-14 12:32                   ` Luciano Coelho
2009-12-14 12:40                     ` David Miller
2009-12-14 13:52                     ` John W. Linville
2009-12-14 14:16 ` Bartlomiej Zolnierkiewicz
2009-12-14 14:26   ` John W. Linville
2009-12-14 14:59     ` Bartlomiej Zolnierkiewicz [this message]
2009-12-14 15:23       ` David Miller
2009-12-14 16:20         ` Bartlomiej Zolnierkiewicz
2009-12-14 18:03           ` David Miller
2009-12-14 18:24             ` Bartlomiej Zolnierkiewicz
2009-12-14 18:41               ` David Miller
2009-12-14 19:16                 ` Bartlomiej Zolnierkiewicz
2009-12-14 19:23                   ` David Miller
2009-12-14 19:42                     ` Bartlomiej Zolnierkiewicz
2009-12-14 19:46                       ` David Miller
2009-12-14 20:09                         ` Bartlomiej Zolnierkiewicz
2009-12-14 15:19     ` David Miller
2009-12-14 16:18       ` Bartlomiej Zolnierkiewicz

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=200912141559.29282.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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;
as well as URLs for NNTP newsgroup(s).