From: Randy Dunlap <randy.dunlap@oracle.com>
To: bryan.wu@analog.com
Cc: Mike Frysinger <vapier.adi@gmail.com>,
Paul Mundt <lethal@linux-sh.org>, Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] Blackfin arch: add kdebug header file
Date: Tue, 27 Mar 2007 08:34:37 -0700 [thread overview]
Message-ID: <20070327083437.e1d6b954.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1174974045.6966.26.camel@roc-desktop>
On Tue, 27 Mar 2007 13:40:45 +0800 Wu, Bryan wrote:
> On Mon, 2007-03-26 at 22:27 -0700, Randy Dunlap wrote:
> > On Tue, 27 Mar 2007 01:17:06 -0400 Mike Frysinger wrote:
> >
> > > On 3/27/07, Paul Mundt <lethal@linux-sh.org> wrote:
> > > > On Tue, Mar 27, 2007 at 12:34:25AM -0400, Mike Frysinger wrote:
> > > > > On 3/26/07, Paul Mundt <lethal@linux-sh.org> wrote:
> > > > > >You should really consider the latter for getting updates merged in the
> > > > > >future
> > > > >
> > > > > we're planning for this, but the short term it isnt doable for us
> > > >
> > > > If you think mangling patches by hand is a more effective use of time, no
> > > > one is stopping you -- some people even prefer that. On the other hand, if
> > > > you're struggling with an effective methodology before things are merged,
> > > > what reason is there to suspect that things will get better afterwards?
> > >
> > > we have a lot of infrastructure that the SCM is part of and at the
> > > moment, git is not a supported SCM
> > >
> > > i'm not saying the current system is easy, just that we cant integrate
> > > git in the short term, so we'll continue spanking Bryan with the
> > > overhead :/
> >
> > In that case, Bryan may like to know that git, mercurial (IIRC),
> > and quilt have patchbomb tools. Also GregKH has one somewhere (he
> > can tell you where). And Paul Jacksone has one at
> > http://www.speakeasy.org/~pj99/sgi/sendpatchset
> >
>
> Thanks for this guide line information. I will dig into it.
>
> But in my experience, it is difficult to find right patch email
> receivers, even in the MAINTAINERS file. If there are 20 patch emails,
> we should find 20 email receivers at least and manually add them to the
> emails. This is terrible, right? Any idea?
Yes, well, we all have the honor of going thru that. There have
been a few suggestions, but I haven't seen any that were Real Good IMO.
You'll learn (quickly) where most patches go (i.e., subsystems and
their major maintainers/contributors). Just put those people into
your email client address book and into the patch descriptions, like
Sam said, so that the patchbomb tools can help you out with them.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-03-27 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:12 Wu, Bryan
2007-03-26 21:45 ` Arnd Bergmann
2007-03-27 3:40 ` Wu, Bryan
2007-03-27 3:57 ` Paul Mundt
2007-03-27 4:34 ` Mike Frysinger
2007-03-27 4:49 ` Paul Mundt
2007-03-27 5:17 ` Mike Frysinger
2007-03-27 5:27 ` Randy Dunlap
2007-03-27 5:40 ` Wu, Bryan
2007-03-27 8:27 ` Sam Ravnborg
2007-03-27 15:34 ` Randy Dunlap [this message]
2007-03-28 2:06 ` Wu, Bryan
2007-03-28 2:13 ` Randy Dunlap
2007-03-27 5:32 ` Wu, Bryan
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=20070327083437.e1d6b954.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bryan.wu@analog.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.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
Powered by JetHome