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

Re: Bug report : bad filter-branch (OSX only)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 29, 2015, 16:30 UTC
Message-ID
<xmqqioce6gon.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20150429154857.GA13518@peff.net>
Jeff King <peff@peff.net> writes:
Show 26 quoted lines
> On Tue, Apr 28, 2015 at 10:39:44PM -0700, Junio C Hamano wrote:
>
>> Jeff King <peff@peff.net> writes:
>> 
>> > I'm not sure of a solution short of replacing the use of sed here with
>> > something else. perl would be a simple choice, but filter-branch does
>> > not otherwise depend on it. We could use a shell "read" loop, but those
>> > are quite slow (and filter-branch is slow enough as it is!).
>> 
>> You need to only skip the header part, right?
>> I would imagine that
>> 
>> (
>> 	while read x && test -n "$x"
>>         do
>>         	:;
>> 	done
>> 	cat
>> ) <../commit | eval "$filter_msg"
>> 
>> would not spin too much in shell loop, perhaps?
>
> Yeah, that is not too bad. Probably we want "read -r", just in case of
> weirdness in the header lines (and that's in POSIX, and we use it
> in other scripts, so it should be portable enough). And we can save a
> subshell if we don't mind the potential variable-name conflict.

As all we care about is "have we hit an empty line", I do not think "-r" really matters, but it would not hurt.

As to s/()/{}/, please tell me what I am doing wrong. I am getting the same process IDs from all of the $$s and the only difference seems to be variable clobbering.

-- >8 -- #!/bin/sh

cat >/var/tmp/tester <<EOF || exit a b

c d EOF

x=foo
echo "My id is $$"
(
	echo "inside paren $$"
	while read x && test -n "$x"
	do
		:;
	done
	cat
) </var/tmp/tester
echo "x=<$x>"
x=foo
{
	echo "inside brace $$"
	while read x && test -n "$x"
	do
		:;
	done
	cat
} </var/tmp/tester
echo "x=<$x>"
Previous: Jeff KingNext: Jeff King
Message 8 of 12 in “Bug report : bad filter-branch (OSX only)”
  1. Olivier ROLANDApr 26, 2015
  2. Jeff KingApr 28, 2015
  3. Olivier ROLANDApr 28, 2015
  4. Jeff KingApr 29, 2015
  5. Jeff KingApr 29, 2015
  6. Junio C HamanoApr 29, 2015
  7. Jeff KingApr 29, 2015
  8. Junio C HamanoApr 29, 2015
  9. Jeff KingApr 29, 2015
  10. Junio C HamanoApr 29, 2015
  11. Johannes SixtApr 29, 2015
  12. Roberto TyleyApr 29, 2015

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.