git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCHv2 2/2] git-p4: initial demonstration of possible RCS keyword fixup

From
Luke Diamand <luke@diamand.org>
Date
Feb 12, 2012, 20:07 UTC
Message-ID
<4F381BE4.2070807@diamand.org>
In-Reply-To
<20120211234248.GA16691@padd.com>
On 11/02/12 23:42, Pete Wyckoff wrote:
Show 6 quoted lines
>
> 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.
Show 10 quoted lines
>
> 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
Previous: Pete WyckoffNext: Junio C Hamano
Message 6 of 7 in “[RFC/PATCHv2 0/2] git-p4: possible RCS keyword fixes”
  1. Luke DiamandFeb 9, 2012
  2. 1/2 git-p4: add test case for RCS keywordsLuke Diamand, Feb 9, 2012
  3. 2/2 git-p4: initial demonstration of possible RCS keyword fixupLuke Diamand, Feb 9, 2012
  4. Pete WyckoffFeb 11, 2012
  5. git-p4: more RCS testsPete Wyckoff, Feb 11, 2012
  6. Luke DiamandFeb 12, 2012
  7. Junio C HamanoFeb 9, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.