From: Jeff Garzik <jeff@garzik.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [bug] build failure in net/netfilter/nf_conntrack_sip.c, on latest -git
Date: Mon, 21 Apr 2008 03:23:52 -0400 [thread overview]
Message-ID: <480C4108.6050709@garzik.org> (raw)
In-Reply-To: <20080419100034.GA9475@elte.hu>
Ingo Molnar wrote:
> 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?
That's in the realm of maintainer choice, much like plenty of other
engineering practices. There is no "rule" as such.
Jeff
prev parent reply other threads:[~2008-04-21 7:24 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
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 [this message]
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=480C4108.6050709@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox