public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@vger.kernel.org, gerg@uclinux.org
Subject: Re: [PATCH] m68k/m68knommu: merge MMU and non-MMU string.h
Date: Wed, 08 Sep 2010 14:01:07 +0200	[thread overview]
Message-ID: <m3lj7ctpfg.fsf@hase.home> (raw)
In-Reply-To: <4C8776C5.9030205@snapgear.com> (Greg Ungerer's message of "Wed, 8 Sep 2010 21:43:01 +1000")

Greg Ungerer <gerg@snapgear.com> writes:

> Hmm, good question. Maybe I should generate stand alone patches
> without gits rename detection turned on?

How did you manage to create the patch?  When I try I'm unable to get
this kind of patch even with rename/copy detection (I have set
diff.renamelimit=0 and diff.renames=copies).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2010-09-08 12:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  4:52 [PATCH] m68k/m68knommu: merge MMU and non-MMU string.h Greg Ungerer
2010-09-07 20:35 ` Geert Uytterhoeven
2010-09-07 20:45   ` Geert Uytterhoeven
2010-09-08 11:43   ` Greg Ungerer
2010-09-08 12:01     ` Andreas Schwab [this message]
2010-09-08 12:22       ` Greg Ungerer
2010-09-08 12:41         ` Andreas Schwab
2010-09-08 12:52           ` Geert Uytterhoeven
2010-09-09 19:14     ` Geert Uytterhoeven
2010-09-10  4:36       ` Greg Ungerer
2010-09-10  8:59         ` Geert Uytterhoeven
2010-09-10  9:00         ` Geert Uytterhoeven
2010-09-13  3:22           ` Greg Ungerer
2010-09-13 18:22 ` Geert Uytterhoeven

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=m3lj7ctpfg.fsf@hase.home \
    --to=schwab@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    /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