On Tue, Jul 19, 2016 at 8:54 PM, Antoine Tenart <antoine.tenart@xxxxxx> wrote: > 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 <gitster@xxxxxxxxx> 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"? Well, internal name is still out of your control, but if you want to do something to a worktree you can say "do project0/foo". With 'next' those verbs can be lock and unlock. We probably can make 'worktree list' take filter and show just one worktree (and just add "git worktree show" for that). >> 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. What I had in mind was "git log --decorate=more-than-full", foo/HEAD and foo1/HEAD do not look as good as project0/HEAD and project1/HEAD (*) > Like moving a worktree (or is there a command for this?) Don't touch it. I've been waiting patiently for that patch series to be reviewed :) -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html