From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: If you want me to quit I will quit
Date: Sat, 26 Apr 2008 13:27:17 +0200 [thread overview]
Message-ID: <20080426112717.GA23248@uranus.ravnborg.org> (raw)
In-Reply-To: <20080426110044.GB2252@cs181133002.pp.htv.fi>
Hi Adrian.
> Why do other people get over 100 checkpatch fixes into the tree at once
> or Linus applies patches directly bypassing the maintainers (like the
> one you sent just before [3], which I've also already sent before [4])
> but my patches bitrot forever?
The patches you submit touches all parts of the kernel tree.
And you do a good job in finding the relevant receivers.
To me you are partly in the saem situation as Andrew in that
you handle a great deal of patches touching a lot of different
subsystems.
We all know that the patch acceptance ratio differ a lot between
the different maintainers and the way Andrew deals with this
seems quite effective.
After enough tries Andrew just submit the pacthes himself direct
to Linus. But almost never without trying to get the relevant
Maintainer to take it first.
So in your position I would keep all patches in
a place so they can be sucked into -next and regular spam
the relevant amintainers with their patches.
When the merge window opens then submit the rest to Linus
with a noe that they have been sent to Maintainers without
any feedback previously.
This is not far away from what you do now and should not create
that big frustrations (I hope).
Sam
next prev parent reply other threads:[~2008-04-26 11:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 6:14 [BUILDFIX PATCH] au0828: debug is a poor global identifier Harvey Harrison
2008-04-26 11:00 ` If you want me to quit I will quit Adrian Bunk
2008-04-26 11:27 ` Sam Ravnborg [this message]
2008-04-26 14:44 ` Adrian Bunk
2008-04-26 16:51 ` Linus Torvalds
2008-04-26 17:09 ` Adrian Bunk
2008-04-26 17:21 ` Linus Torvalds
2008-04-26 17:35 ` Adrian Bunk
2008-04-26 17:56 ` Linus Torvalds
2008-04-26 14:51 ` Andrew Morton
2008-04-26 15:23 ` Adrian Bunk
2008-04-26 15:44 ` Andrew Morton
2008-04-26 17:16 ` Adrian Bunk
2008-04-26 17:20 ` Andrew Morton
2008-04-26 17:27 ` Adrian Bunk
2008-04-26 17:35 ` Linus Torvalds
2008-04-26 17:31 ` Linus Torvalds
2008-04-26 17:42 ` Sam Ravnborg
2008-04-26 18:26 ` Linus Torvalds
2008-04-26 18:51 ` Stefan Richter
2008-04-26 19:05 ` Linus Torvalds
2008-04-26 19:18 ` Linus Torvalds
2008-04-26 20:30 ` Andrew Morton
2008-04-26 20:35 ` Linus Torvalds
2008-04-28 19:05 ` Romano Giannetti
2008-04-26 20:49 ` Stefan Richter
2008-04-27 12:07 ` Richard Purdie
2008-04-27 14:28 ` Stefan Richter
2008-04-26 19:43 ` Stefan Richter
2008-04-27 0:31 ` David Miller
2008-04-27 2:58 ` Jeff Garzik
2008-04-27 16:09 ` Ingo Molnar
2008-04-26 16:21 ` Bartlomiej Zolnierkiewicz
2008-04-26 17:10 ` Adrian Bunk
2008-04-26 19:20 ` Harvey Harrison
2008-04-26 19:42 ` Adrian Bunk
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=20080426112717.GA23248@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome