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

Re: [PATCH] worktree: allow "-" short-hand for @{-1} in add command

From
JGJordan DE GEA <jordan.de-gea@grenoble-inp.org>
Date
May 27, 2016, 12:43 UTC
Message-ID
<9975E0C6-7BCC-4D80-BBC6-2C0BAB13D3E6@grenoble-inp.org>
In-Reply-To
<xmqqshx4vedr.fsf@gitster.mtv.corp.google.com>
Show 6 quoted lines
>> +test_expect_success '"add" using shorthand - fails when no previous branch' '
>> +	test_must_fail git worktree add existing -
>> +'
> 
> Just an observation, but the error message we would see here might
> be interesting.
Of course, that’s useful to be sure of the error, I will do in next preroll.
Show 25 quoted lines
> 
>> +	branch=$(cd short-hand && git rev-parse --symbolic-full-name HEAD) &&
>> +	test "$branch" = refs/heads/newbranch &&
>> +	cd ..
> 
> If any of the command between "cd short-hand" and "cd .." failed,
> after correcting the broken &&-chain, the next test will end up
> running in short-hand directory, which it is not expecting.  A
> canonical way to avoid this problem is to replace the above with:
> 
> 	...
>        git worktree add short-hand - &&
>        (
> 		cd short-hand &&
>                ...
>                test "$branch" = refs/heads/newbranch
> 	)
> 
> In this particular case, alternatively, you could also do something
> like this:
> 
>        git worktree add short-hand - &&
> 	echo refs/heads/newbranch >expect &&
> 	git -C short-hand rev-parse --symbolic-full-name HEAD >actual &&
> 	test_cmp expect actual
Yes, that’s a good idea. I take these lines. 
Previous: Junio C HamanoNext: Jordan DE GEA
Message 5 of 7 in “worktree: allow "-" short-hand for @{-1} in add command”
  1. worktree: allow "-" short-hand for @{-1} in add commandJordan DE GEA, May 26, 2016
  2. Junio C HamanoMay 26, 2016
  3. Matthieu MoyMay 27, 2016
  4. Junio C HamanoMay 27, 2016
  5. Jordan DE GEAMay 27, 2016
  6. worktree: allow "-" short-hand for @{-1} in add commandJordan DE GEA, May 27, 2016
  7. Junio C HamanoMay 27, 2016

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.