Re: [PATCH 2/2] filter-branch: fail gracefully when a filter fails
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 5, 2007, 16:52 UTC
- Message-ID
- <7vk5tedc8c.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <Pine.LNX.4.64.0707051636240.9789@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 16 quoted lines
> On Thu, 5 Jul 2007, Jeff King wrote: > >> status=`((cmd1; echo $? >&3) | cmd2) 3>&1` > > Cute. > > This is the replacement patch, then (I guess there are still some nits to > be had, so I did not redo the proper patch yet): > ... > + (sed -e '1,/^$/d' <../commit | > + (eval "$filter_msg" || > + die "msg filter failed: $filter_msg" 2>&3) | > + (sh -c "$filter_commit" "git commit-tree" $(git write-tree) \ > + $parentstr > ../map/$commit || > + die "commit filter failed: $filter_commit" 2>&3)) 3>&1 | > + grep . && die
You certainly meant "grep >&2 ." at the end of that pipeline; while I welcome people to be aware that it is possible with esoteric shell redirection games, I personally feel this is not worth it.