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

Re: 195b7ca6 breaks t9010 at current master

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Mar 31, 2011, 21:14 UTC
Message-ID
<20110331211443.GC19932@elie>
In-Reply-To
<YHiIPkNCiU3RcX-PxtGuaAPfpIMSLtDzcuGX-pUHbb_4SC5aAQu_WQ@cipher.nrlssc.navy.mil>
Hi,
Brandon Casey wrote:
Show 17 quoted lines
> I was just about to send a patch for this, when I noticed it has
> already been worked around in master by the above.
>
> I'll still share my one-liner for informational purposes which uses perl
> and in my opinion is a little simpler:
>
> --- a/t/t9010-svn-fe.sh
> +++ b/t/t9010-svn-fe.sh
> @@ -465,7 +465,7 @@ test_expect_success 'NUL in log message, file content, and property name' '
>                 git diff-tree --root --stdin |
>                 sed "s/$_x40/OBJID/g"
>         } >actual &&
> -       git cat-file commit HEAD | nul_to_q | sed -ne "/^\$/,\$ p" >actual.message &&
> +       git cat-file commit HEAD | nul_to_q | perl -ne "print if (/^$/..eof())" >actual.message &&
>         git cat-file blob HEAD^:greeting | nul_to_q >actual.hello1 &&
>         git cat-file blob HEAD:greeting | nul_to_q >actual.hello2 &&
>         test_cmp expect actual &&

Thanks. I'll definitely use that idiom the next time this sed gotcha comes up.

Also if you're interested, I'd be happy to take a patch on top to make it so as a cleanup (probably splitting the line at the same time, since it's getting pretty long).

Previous: Brandon Casey
Message 7 of 7 in “195b7ca6 breaks t9010 at current master”
  1. Øyvind A. HolmMar 29, 2011
  2. Jonathan NiederMar 29, 2011
  3. Brian GernhardtMar 29, 2011
  4. [PULL svn-fe] Re: 195b7ca6 breaks t9010 at current masterJonathan Nieder, Mar 29, 2011
  5. Øyvind A. HolmMar 29, 2011
  6. Brandon CaseyMar 31, 2011
  7. Jonathan NiederMar 31, 2011

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.