From: Jeff King <peff@peff.net>
To: Petr Onderka <gsvick@gmail.com>
Cc: git@vger.kernel.org, Bjorn Steinbrink <B.Steinbrink@gmx.de>,
Paolo Bonzini <bonzini@gnu.org>
Subject: Re: [PATCH] Userdiff patterns for C#
Date: Wed, 11 Aug 2010 15:37:39 -0400 [thread overview]
Message-ID: <20100811193739.GC8106@coredump.intra.peff.net> (raw)
In-Reply-To: <1281488961-5884-1-git-send-email-gsvick@gmail.com>
On Wed, Aug 11, 2010 at 01:09:21AM +0000, Petr Onderka wrote:
> Add userdiff patterns for C#. This code is an improved version of
> code by Adam Petaccia from 21 June 2009 mail to the list.
> [...]
> t/t4018-diff-funcname.sh | 2 +-
> userdiff.c | 16 ++++++++++++++++
> 2 files changed, 17 insertions(+), 1 deletions(-)
Can you also add a line in Documentation/gitattributes.txt so that
people know your pattern is there? In the "custom hunk-header"
section, there is already a list to add to.
-Peff
next prev parent reply other threads:[~2010-08-11 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 1:09 [PATCH] Userdiff patterns for C# Petr Onderka
2010-08-11 19:37 ` Jeff King [this message]
2010-08-16 17:01 ` [PATCH v2] " Petr Onderka
2010-08-16 17:14 ` Jeff King
2010-08-22 7:23 ` Junio C Hamano
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=20100811193739.GC8106@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=B.Steinbrink@gmx.de \
--cc=bonzini@gnu.org \
--cc=git@vger.kernel.org \
--cc=gsvick@gmail.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;
as well as URLs for NNTP newsgroup(s).