From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, kaber@trash.net,
torvalds@linux-foundation.org, akpm@linux-foundation.org
Subject: Re: [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git
Date: Sat, 19 Apr 2008 12:39:42 +0200 [thread overview]
Message-ID: <20080419103942.GA13599@elte.hu> (raw)
In-Reply-To: <20080419.030337.244502148.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> From: Ingo Molnar <mingo@elte.hu>
> Date: Sat, 19 Apr 2008 12:00:35 +0200
>
> > btw., i found no thread to reply to on lkml or elsewhere - arent all
> > git pull requests supposed to be Cc:-ed to lkml, with shortlog
> > included?
>
> I have never once done this even going all the way back to the BK
> days.
do you find this practice of private pull requests important? If not,
would it be difficult to Cc: lkml to routine pull requests?
> I always send my pull requests directly to Linus, CC:'ing Andrew.
that makes bugs harder to report and makes the flow of patches harder to
follow as well. Often (like in this case) i see it when a bug comes in
via a specific group of commits but i have no time to do a bisection. In
that case i'd like to report it to that pull request so i'd like to
reply to that pull on lkml.
But in this case i first did an unsuccessful full-text search on lkml,
then i also opened up netdev and did a full text search there too to
find the originator pull request or the patches but the search turned up
nothing. As the number of subsystems increases, i suspect you agree with
me that this does not scale very well for bug reporters, correct?
i'm convinced that testers and bug reporters are the scarce resource
these days, not patch integrators and not maintainers which was the
scarce resource 3-4 years ago, before Git and before BK. It is testing
(and review) capacity that limits the growth of Linux today, not patch
writing and patch integration capacity.
Ingo
next prev parent reply other threads:[~2008-04-19 10:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 10:00 [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git Ingo Molnar
2008-04-19 10:03 ` David Miller
2008-04-19 10:39 ` Ingo Molnar [this message]
2008-04-19 11:09 ` David Miller
2008-04-21 8:22 ` Ingo Molnar
2008-04-21 8:58 ` David Miller
2008-04-21 11:14 ` Ingo Molnar
2008-04-21 16:26 ` [bug] build failures, git trees Randy Dunlap
2008-04-21 21:42 ` David Miller
2008-04-21 11:18 ` [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git Patrick McHardy
2008-04-21 19:31 ` Ingo Molnar
2008-04-21 8:14 ` Jeff Garzik
2008-04-21 13:39 ` Ingo Molnar
2008-04-22 2:20 ` Herbert Xu
2008-04-19 10:07 ` David Miller
2008-04-19 10:41 ` Ingo Molnar
2008-04-19 11:10 ` David Miller
2008-04-19 10:44 ` Jan Engelhardt
2008-04-19 11:11 ` David Miller
2008-04-19 16:38 ` Patrick McHardy
2008-04-20 0:54 ` David Miller
2008-04-21 7:23 ` Jeff Garzik
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=20080419103942.GA13599@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.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 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.