mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: James.Bottomley@HansenPartnership.com,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	Russell King <rmk@arm.linux.org.uk>,
	lkml <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [RFC] [PATCH] linux-2.5.49_subarch-cleanup_A2
Date: 26 Nov 2002 12:16:09 -0800	[thread overview]
Message-ID: <1038341769.956.49.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <20021126195427.GB1525@mars.ravnborg.org>

On Tue, 2002-11-26 at 11:54, Sam Ravnborg wrote:
> One detail..
> Move the "mcore-y := mach-default" assignment above the
> block that deal with subarch. Then you do not need the "ifndef ..."

Ah, good suggestion! Thanks! I'll apply and resubmit later today.

> I recall that Linus previously have asked for shell commands
> when moving files - so consider including only the patch below and
> then a number of "mv arch/i386/X include/....".
> This makes it much more visible what you actually change.
> 
> Another alternative it to do it in bitkeeper, then it is visible
> from the cset that you move files (use bk mv).

Hmm. I was under the impression that shell command and sed script
patches were only for those w/ enough kernel penguin points to blow.
Although, please someone correct me if I'm wrong.  Regardless BK should
notice the renames in the diff and import them as such, so it shouldn't
make much difference to Linus. 

Thanks again for the feedback!

-john


      reply	other threads:[~2002-11-26 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  1:40 john stultz
2002-11-26 19:54 ` Sam Ravnborg
2002-11-26 20:16   ` john stultz [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=1038341769.956.49.camel@w-jstultz2.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®