On Tue, Jul 19, 2016 at 08:23:58PM +0200, Duy Nguyen wrote: > On Tue, Jul 19, 2016 at 8:04 PM, Junio C Hamano <gits...@pobox.com> wrote: > > 080739b (worktree.c: find_worktree() search by path suffix - > 2016-06-13) from 'next' should help identify worktrees in this case by > specifying 'project0/foo', 'project1/foo'... Granted it's not fun to > type all that when 'project0/foo' is something long, and bash > completion probably does not help much either.
So with this I'll be able to create new worktrees, using paths having the same basename, but in different let's say "project directories"? > Note that we may need a unique name elsewhere too, e.g. > refs/worktrees/xyz (even though we haven't settled on this yet). Then > xyz would be more exposed to the user and an easily recognizable name > would be a good thing. Having a recognisable name surely is a good thing, when performing some (rare) manual operations. Like moving a worktree (or is there a command for this?) Thanks, -- Antoine
signature.asc
Description: PGP signature