All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: David Howells <dhowells@redhat.com>,
	akpm@linux-foundation.org, sam@ravnborg.org,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: patch(1) and git -M output (Re: [PATCH 2/2] FRV: Move to arch/frv/include/asm/)
Date: Fri, 10 Apr 2009 00:06:54 +0200	[thread overview]
Message-ID: <200904100006.54473.agruen@suse.de> (raw)
In-Reply-To: <20090409182803.GE26366@ZenIV.linux.org.uk>

On Thursday, 9 April 2009 20:28:03 Al Viro wrote:
> On Thu, Apr 09, 2009 at 07:13:29PM +0100, Al Viro wrote:
> > We can teach patch(1) to handle those - apparently agruen has resurrected
> > development lately (git://git.savannah.gnu.org/patch.git), so it might
> > be possible without usual latency problems...
>
> From the quick look it appears that src/pch.c::intuit_diff_type() is the
> place where it could be done, with inname and outfile set according to
> rename from/rename to lines.  Might need some flag to make the damn thing
> reset outfile when we are done with this one; hopefully, the next call
> of intuit_diff_type() wouldn't be too late for that, but that's just from
> a very cursory reading of the code.
>
> Andreas, do you have anything of that kind queued?

I've flushed my queue over the last weeks; nothing significant is pending 
right now.  At the moment I'm trying to stabilize patch for the next stable 
release, which is supposed to happen in about a month's time.  Anything major 
would go into the release after that.

> If not, I'll probably take a stab at that (handling git -M output, that is).

Patches are welcome. (I hope you won't mind the GNU copyright assignment / 
disclaimer paperwork.)

Thanks,
Andreas

  reply	other threads:[~2009-04-09 22:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 16:32 [PATCH 1/2] FRV: Use <asm-generic/pgtable.h> in NOMMU mode David Howells
2009-04-09 16:33 ` [PATCH 2/2] FRV: Move to arch/frv/include/asm/ David Howells
2009-04-09 17:51   ` Linus Torvalds
2009-04-09 18:04     ` Linus Torvalds
2009-04-09 18:13     ` Al Viro
2009-04-09 18:26       ` Linus Torvalds
2009-04-09 18:39         ` Al Viro
2009-04-09 18:28       ` patch(1) and git -M output (Re: [PATCH 2/2] FRV: Move to arch/frv/include/asm/) Al Viro
2009-04-09 22:06         ` Andreas Gruenbacher [this message]
2009-04-09 23:21           ` Al Viro
2009-04-09 21:05     ` [PATCH 2/2] FRV: Move to arch/frv/include/asm/ David Howells
2009-04-09 21:18       ` Linus Torvalds
2009-04-09 21:23         ` Randy Dunlap
2009-04-09 21:51         ` David Howells
2009-04-09 22:00           ` Linus Torvalds
2009-04-09 23:24             ` Fix for StGIT David Howells

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=200904100006.54473.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.