From: Luke Diamand <luke@diamand.org>
To: Pete Wyckoff <pw@padd.com>
Cc: git@vger.kernel.org, Eric Scouten <eric@scouten.com>
Subject: Re: [RFC/PATCHv2 2/2] git-p4: initial demonstration of possible RCS keyword fixup
Date: Sun, 12 Feb 2012 20:07:00 +0000 [thread overview]
Message-ID: <4F381BE4.2070807@diamand.org> (raw)
In-Reply-To: <20120211234248.GA16691@padd.com>
On 11/02/12 23:42, Pete Wyckoff wrote:
>
> I'll send along a bunch of test cases I wrote to play around
> with this. Your case had too many moving parts for me to
> understand. If there's something in there that isn't covered,
> maybe you can factor it out into something small? Feel free
> to merge any of my code in with a future resubmission.
Thanks - I'm glad you like it! I'll rework it with your code and resubmit.
>
> Some comments in this code below:
>
>
> This is a novel approach too. Instead of just guessing that
> keywords are causing the conflict, inspect the diff for context
> or edited lines containing keywords.
>
> Or we could just always scrub every file before even trying to
> apply patches.
I guess scrubbing every file could get quite slow. We have people
checking in hundreds of megabytes of C test vectors....
>
> In a few spots I see you've taken the ":" out of the regex. This
> will match strings like $Idiot$ that shouldn't be keyword
> expanded.
Good point - I'll put the ':' back.
>
> Impressed.
Thanks!
Updated patch series to follow.
Luke
next prev parent reply other threads:[~2012-02-12 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 23:17 [RFC/PATCHv2 0/2] git-p4: possible RCS keyword fixes Luke Diamand
2012-02-09 23:17 ` [RFC/PATCHv2 1/2] git-p4: add test case for RCS keywords Luke Diamand
2012-02-09 23:17 ` [RFC/PATCHv2 2/2] git-p4: initial demonstration of possible RCS keyword fixup Luke Diamand
2012-02-11 23:42 ` Pete Wyckoff
2012-02-11 23:44 ` [PATCH] git-p4: more RCS tests Pete Wyckoff
2012-02-12 20:07 ` Luke Diamand [this message]
2012-02-09 23:29 ` [RFC/PATCHv2 0/2] git-p4: possible RCS keyword fixes 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=4F381BE4.2070807@diamand.org \
--to=luke@diamand.org \
--cc=eric@scouten.com \
--cc=git@vger.kernel.org \
--cc=pw@padd.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).