linux-kernel - Re: [PATCH -mm] Blackfin arch: add kdebug header file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070327083437.e1d6b954.randy.dunlap@oracle.com>
Date:	Tue, 27 Mar 2007 08:34:37 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	bryan.wu@...log.com
Cc:	Mike Frysinger <vapier.adi@...il.com>,
	Paul Mundt <lethal@...ux-sh.org>,
	Arnd Bergmann <arnd@...db.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm] Blackfin arch: add kdebug header file

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@...ux-sh.org> wrote:
> > > > On Tue, Mar 27, 2007 at 12:34:25AM -0400, Mike Frysinger wrote:
> > > > > On 3/26/07, Paul Mundt <lethal@...ux-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 ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/