From: Ralf Baechle <ralf@oss.sgi.com>
To: Ivan Hamilton <ivan@chimerical.com.au>
Cc: linux-mips@oss.sgi.com
Subject: Re: Inclusion of rrm.o in export-objs
Date: Fri, 16 Nov 2001 02:54:20 +1100 [thread overview]
Message-ID: <20011116025420.C6317@dea.linux-mips.net> (raw)
In-Reply-To: <4DF7FE7DA7E47442B859983ABCFBBF627971@chimsvr1.chimerical.com.au>; from ivan@chimerical.com.au on Fri, Nov 16, 2001 at 12:38:46AM +1100
On Fri, Nov 16, 2001 at 12:38:46AM +1100, Ivan Hamilton wrote:
> My Makefile knowledge is extremely limited to say the least. But are
> there possible side-effects of this particular fix? And how does a fix
> like this, find it's way back into the source tree?
Fixed in CVS. And yes, your fix was correct.
Ralf
prev parent reply other threads:[~2001-11-15 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 13:38 Inclusion of rrm.o in export-objs Ivan Hamilton
2001-11-15 13:38 ` Ivan Hamilton
2001-11-15 15:54 ` 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=20011116025420.C6317@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=ivan@chimerical.com.au \
--cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.