From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932439AbXC1CHm (ORCPT ); Tue, 27 Mar 2007 22:07:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933403AbXC1CHm (ORCPT ); Tue, 27 Mar 2007 22:07:42 -0400 Received: from nwd2mail10.analog.com ([137.71.25.55]:9512 "EHLO nwd2mail10.analog.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932439AbXC1CHk (ORCPT ); Tue, 27 Mar 2007 22:07:40 -0400 X-IronPort-AV: i="4.14,336,1170651600"; d="scan'208"; a="32825287:sNHT23490411" Subject: Re: [PATCH -mm] Blackfin arch: add kdebug header file From: "Wu, Bryan" Reply-To: bryan.wu@analog.com To: Randy Dunlap Cc: bryan.wu@analog.com, Mike Frysinger , Paul Mundt , Arnd Bergmann , Andrew Morton , linux-kernel@vger.kernel.org In-Reply-To: <20070327083437.e1d6b954.randy.dunlap@oracle.com> References: <1174903941.32691.72.camel@roc-desktop> <200703262345.09489.arnd@arndb.de> <1174966837.6966.13.camel@roc-desktop> <20070327035734.GA25883@linux-sh.org> <8bd0f97a0703262134h20bdf8dcqb1043ca176a7149c@mail.gmail.com> <20070327044914.GA26099@linux-sh.org> <8bd0f97a0703262217g16aa62d4g1221082deda0aed2@mail.gmail.com> <20070326222711.d2f42da2.randy.dunlap@oracle.com> <1174974045.6966.26.camel@roc-desktop> <20070327083437.e1d6b954.randy.dunlap@oracle.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Analog Devices, Inc. Date: Wed, 28 Mar 2007 10:06:13 +0800 Message-Id: <1175047573.15391.2.camel@roc-desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2007-03-27 at 08:34 -0700, Randy Dunlap wrote: > 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 wrote: > > > > > On Tue, Mar 27, 2007 at 12:34:25AM -0400, Mike Frysinger wrote: > > > > > > On 3/26/07, Paul Mundt 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. > Thanks a lot, I will try on my side. And one more question: What is patchbomb tools, you mean git, quilt or other kernel patch management tool? I am using quilt and try to use git to manage patches. Is there a tool just named patchbomb? Best Regards, -Bryan