linux-wireless.vger.kernel.org archive mirror
 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 21:09:38 +0100	[thread overview]
Message-ID: <200912142109.38697.bzolnier@gmail.com> (raw)
In-Reply-To: <20091214.114652.243547684.davem@davemloft.net>

On Monday 14 December 2009 08:46:52 pm David Miller wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Date: Mon, 14 Dec 2009 20:42:13 +0100
> 
> > However looking at "Top non-author signoffs in 2.6.31" [1]:
> > 
> > David S. Miller     964 10.1%
> > Ingo Molnar         948 9.9%
> > Greg Kroah-Hartman  582 6.1%
> > ...
> > 
> > it seems that there are people able to do large upstream merges in much
> > more transparent and reviewer-friendly way so it is not like there exists
> > some real physical barrier for not even trying to do things better..
> 
> Greg (USB, staging) and Ingo (scheduler, perf, tracing, x86) each work
> in several disconnected areas, and have you seen the size of the

I would risk saying that in Ingo's case those areas are frequently more
inter-connected than i.e. wireless driver changes and core networking ones...

> staging tree merges? :-)

..and yes, I did take a look at 2.6.33 staging merge before writing my mail.

I think that it was too big personally but it was still only 235 commits:

commit 0e2f7b837600979d5b6f174a6ff695b85942e985
Merge: f58df54 032fec3
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Dec 11 15:25:56 2009 -0800

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6

    * git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6: (235 commits)

1815 networking commits means almost 8x more and while LOC amount for staging
is much higher, networking changes affect 2x more files.

--
Bartlomiej Zolnierkiewicz

  reply	other threads:[~2009-12-14 20:11 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
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 [this message]
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=200912142109.38697.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).