Re: [PATCH 3/3] fetch: Use the remote's ref name to decide how to describe new refs.
- From
Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
- Date
- Apr 17, 2012, 07:53 UTC
- Message-ID
- <4F8D2195.9030507@in.waw.pl>
- In-Reply-To
- <20120416223429.GA13440@burratino>
On 04/17/2012 12:34 AM, Jonathan Nieder wrote:
Show 13 quoted lines
> marcnarc@xiplink.com wrote: > >> + grep descriptive-branch actual | grep "[new branch]"&& >> + grep descriptive-tag actual | grep "[new tag]"&& >> + grep others/crazy actual | grep "[new ref]" > > Careful. :) I suppose the simplest fix would be to leave out the > brackets so the '[new ref]' tag is not misinterpreted as a character > class, like so: > > grep "new branch.*descriptive-branch" actual&& > grep "new tag.*descriptive-tag" actual&& > grep "new ref.*others/crazy" actual
s/grep/test_i18ngrep/
Also:
Show 7 quoted lines
>> + echo "Nuts" >> crazy && >> + git add crazy && >> + git commit -a -m "descriptive commit" && >> + git update-ref refs/others/crazy HEAD && >> + ( >> + cd descriptive && >> + git fetch o 2> actual
redirections should be without spaces between '>' and the filename (>>crazy, 2>actual), for portability.
Zbyszek