All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: Revised wireless tree management practices
Date: Mon, 14 Dec 2009 19:24:47 +0100	[thread overview]
Message-ID: <200912141924.47370.bzolnier@gmail.com> (raw)
In-Reply-To: <20091214.100345.57458443.davem@davemloft.net>

On Monday 14 December 2009 07:03:45 pm David Miller wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Date: Mon, 14 Dec 2009 17:20:11 +0100
> 
> > Well, in theory all maintainers should be testing -next kernels
> > so nothing should change also in this regard.
> 
> You conveniently did not quote and respond to my comments showing that
> you can ask git tools to seperate out the changesets for you, regardless
> of what subsystem maintainers decide to do.
> 
> Power is in your hands, really. :-)

That is simply untrue from Linus' kernel point of view.

Each networking merge contains multiple sub-merges from wireless tree
(at random points in networking tree history) which in turn may contain
multiple sub-merges from Johannes (at random points in wireless tree
history) and wireless driver sub-projects so unless you are a hardcore
networking/wireless developer it is practically impossible to make
a sense out of it in a reasonable time.

--
Bartlomiej Zolnierkiewicz

  reply	other threads:[~2009-12-14 18:26 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
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 [this message]
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=200912141924.47370.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 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.