From: Alan Modra <amodra@bigpond.net.au>
To: cgd@broadcom.com
Cc: binutils@sources.redhat.com
Subject: Re: replace mips-*n*bsd in
Date: Mon, 28 Apr 2003 23:16:00 -0000 [thread overview]
Message-ID: <20030428231547.GD25514@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <yov5llxutkcu.fsf@broadcom.com>
On Mon, Apr 28, 2003 at 01:53:05PM -0700, cgd@broadcom.com wrote:
> I'd like to see the patch below on the trunk and the branch. This
> puts the OS names back, for these targets.
That's fine.
> While i'm all for consolidating, is there any reason to take it that
> far?!
To fit them all on one line? I can't remember why I did it.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2003-04-28 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 20:53 cgd
2003-04-28 23:16 ` Alan Modra [this message]
[not found] ` <mailpost.1051571783.9996@news-sj1-1>
2003-04-28 23:51 ` cgd
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=20030428231547.GD25514@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=cgd@broadcom.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).