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. > > Helped-by: Eric Sunshine <[email protected]> > Signed-off-by: Nguyễn Thái Ngọc Duy <[email protected]> > --- > diff --git a/worktree.h b/worktree.h > @@ -29,6 +29,12 @@ extern struct worktree **get_worktrees(void); > +/* > + * Search a worktree by its path. Paths are normalized internally. > + */ > +extern struct worktree *find_worktree_by_path(struct worktree **list, > + const char *path_); > +
Sorry for not noticing last time, but I'd probably have named this argument 'path' rather than 'path_' here in the header. Not worth a re-roll, of course. -- 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
