Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Carsten Langgaard <carstenl@mips.com>, linux-mips@oss.sgi.com
Subject: Re: Bug in get_insn_opcode.
Date: Sun, 4 Mar 2001 20:48:26 +0100	[thread overview]
Message-ID: <20010304204826.B15182@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10103031614440.455-100000@cassiopeia.home>; from geert@linux-m68k.org on Sat, Mar 03, 2001 at 04:15:05PM +0100

On Sat, Mar 03, 2001 at 04:15:05PM +0100, Geert Uytterhoeven wrote:

> > > Index: arch/mips/kernel/traps.c
> > > ===================================================================
> > > RCS file: /home/repository/sw/linux-2.4.0/arch/mips/kernel/traps.c,v
> > > retrieving revision 1.10
> > > diff -u -r1.10 traps.c
> > > --- traps.c     2001/02/28 13:46:43     1.10
> > > +++ traps.c     2001/03/02 16:50:27
> > 
> > Patch will behave (un-)funny on a cvs diff generated patch like this which
> > lacks full pathnames in the --- and +++ lines.  Patches for this
> > behaviour are available on ftp.cyclic.com (so it still exists ...) or in
> > more recent cvs rpms.
> 
> Isn't patch supposed to look at the `Index' line?

Only when the environment variable POSIXLY_CORRECT is set to y which has
a ton of other unwanted side effects, so patch would need wrapper scripts
or what not else.

  Ralf

      reply	other threads:[~2001-03-04 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-02 16:56 Bug in get_insn_opcode Carsten Langgaard
2001-03-02 18:34 ` Jun Sun
2001-03-03  7:21 ` Ralf Baechle
2001-03-03 15:15   ` Geert Uytterhoeven
2001-03-04 19:48     ` 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=20010304204826.B15182@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=carstenl@mips.com \
    --cc=geert@linux-m68k.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox