On Sun, May 22, 2016 at 6:43 AM, Nguyễn Thái Ngọc Duy <[email protected]> wrote:
> So far we haven't needed to identify an existing worktree from command
> line. Future commands such as lock or move will need it. There are of
> course other options for identifying a worktree, for example by branch
> or even by internal id. They may be added later if proved useful.
Beyond the above methods for specifying a worktree, [1] adds
$(basename $path) as a possibility if not ambiguous. Excerpt:
For git-worktree commands such as "lock", "mv", "remove", it
likely will be nice to allow people to specify the linked
worktree not only by path, but also by tag, and possibly even by
$(basename $path) if not ambiguous.
[1]: http://article.gmane.org/gmane.comp.version-control.git/275528
> Helped-by: Eric Sunshine <[email protected]>
> Signed-off-by: Nguyễn Thái Ngọc Duy <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
