On Wed, Jul 20, 2016 at 04:54:40PM +0200, Duy Nguyen wrote:
> On Tue, Jul 19, 2016 at 9:35 PM, Antoine Tenart wrote:
> >
> > Hmm, so if I understand correctly my use case still won't be supported,
> > as adding a new worktree with the same basename will fail. Or did I m
Hello Eric,
On Tue, Jul 19, 2016 at 02:52:42PM -0400, Eric Sunshine wrote:
> On Tue, Jul 19, 2016 at 2:04 PM, Junio C Hamano wrote:
> > Antoine Tenart writes:
> >> Adds a --name option allowing to specify the name of a worktree when
> >> creating it. This allows to
On Tue, Jul 19, 2016 at 09:04:11PM +0200, Duy Nguyen wrote:
> On Tue, Jul 19, 2016 at 8:54 PM, Antoine Tenart 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 wrote:
> >>
> >> 080739b
On Tue, Jul 19, 2016 at 12:08:11PM -0700, Junio C Hamano wrote:
> Antoine Tenart writes:
>
> > Being able to manually define the name can also be useful in some (rare)
> > cases, where you reorganize your project directory tree. But that's not
> > a strong ar
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 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
Hi,
On Tue, Jul 19, 2016 at 11:04:59AM -0700, Junio C Hamano wrote:
>
> > Adds a --name option allowing to specify the name of a worktree when
> > creating it. This allows to have multiple worktrees in directories
> > having the same name (e.g. project0/foo, project1/foo etc...). This
> > commit
) as the worktree name when the --name option
isn't used.
Two new test cases are added to ensure the --name option does not break
other functionalities and is working properly.
Finally, the documentation is updated to reflect this --name option
addition.
Signed-off-by: Antoine T
7 matches
Mail list logo
