Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Vivien Chappelier <vivien.chappelier@enst-bretagne.fr>
Cc: linux-mips@oss.sgi.com
Subject: Re: lib/Config.in missing in CVS HEAD ?
Date: Thu, 4 Jul 2002 13:29:16 +0200	[thread overview]
Message-ID: <20020704132916.A26943@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0207041317070.1601-200000@melkor>; from vivien.chappelier@enst-bretagne.fr on Thu, Jul 04, 2002 at 01:21:48PM +0200

On Thu, Jul 04, 2002 at 01:21:48PM +0200, Vivien Chappelier wrote:

> 	arch/mips64/config.in includes lib/Config.in which is
> missing. Please either put that file on CVS HEAD if it exists and is
> needed, or update arch/mips64/config.in with the following patch.
> 	Currently, 'make menuconfig ARCH=mips64' crashes because of this.

Now you know that I'm not using menuconfig :-)  Patch applied.

Btw, do me a favor, send patches inline, not as attachment unless your
mailer does funny things to them.

  Ralf

      reply	other threads:[~2002-07-04 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04 11:21 lib/Config.in missing in CVS HEAD ? Vivien Chappelier
2002-07-04 11:29 ` 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=20020704132916.A26943@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=vivien.chappelier@enst-bretagne.fr \
    /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