Re: [PATCH 0/1] Introduce a way to create a branch and worktree at the same time

From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Duy Nguyen <pclouds@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/1] Introduce a way to create a branch and worktree at the same time
Date: Tue, 15 Mar 2016 07:53:41 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1603150746490.4690@virtualbox> (raw)
In-Reply-To: <xmqqmvq5bjlc.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Thu, 10 Mar 2016, Junio C Hamano wrote:

> Duy Nguyen <pclouds@gmail.com> writes:
> 
> >> Granted, "git worktree remove" should be the work horse. But why not have
> >> two ways to skin the same cat? I, again, would prefer the short 'n sweet
> >> "git branch -d -w pull-rebase-prefix" invocation.
> >
> > If you put effort into making it happen, I'm not stopping you :)
> 
> I actually would ;-)  If I had to choose between the two, I'd prefer
> to see this new feature as part of the "worktree" subcommand, simply
> because "branch" is a fairly basic feature that can be used by those
> who are new to Git without knowing that the "worktree" feature even
> exists (hence not having to have one extra option description in its
> documentation that talks about "worktree" is a big plus).

I, in contrast, think it woild make for an excellent way to let users who
are in the dear need for the worktree feature (like myself) find out about
it.

Nobody reads release notes, but at least some people read man pages.

> Personally, I think you are better off implementing this set of
> features as a set of shell aliases (be it bash or tcsh).

True, if I was simply selfish, I would use shell aliases, too.

But I want others to benefit from my work, too, hence the patch.

> That approach to implement the UI that directly faces the end users
> via scripting would let your users choose layouts more flexibly.
> Some people may want a repository and its worktrees next to each
> other, some others may want the worktrees embedded inside the main
> repository, yet some others may want layouts other than those two.

Having the worktree in a totally different location than the associated
repository is *very* confusing. Unless, that is, you work on a single
project, ever, of course, which is a luxury typically only awarded to
maintainers, albeit not this one.

As such, *recommending* to have it elsewhere really is nothing but a
workaround for some bugs that should still be squashed instead.

Ciao,
Dscho