Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] Coalesce duplicated SiByte settings
Date: Thu, 20 Feb 2003 19:31:15 +0100	[thread overview]
Message-ID: <20030220193115.A394@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030220183613.25777I-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Thu, Feb 20, 2003 at 06:41:52PM +0100

On Thu, Feb 20, 2003 at 06:41:52PM +0100, Maciej W. Rozycki wrote:

>  There is quite a lot identical entries for SiByte board variations in the
> top-level architecture Makefiles.  They look confusing and I don't think
> they are necessary.  Following is a proposal to remove duplicated entries. 
> OK? 

Yep, I like this.

  Ralf

      parent reply	other threads:[~2003-02-20 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 17:41 [patch] Coalesce duplicated SiByte settings Maciej W. Rozycki
2003-02-20 17:48 ` Kip Walker
2003-02-20 18:31 ` Ralf Baechle [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=20030220193115.A394@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    /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