From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.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: Thu, 10 Mar 2016 14:24:16 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1603101422190.4690@virtualbox> (raw)
In-Reply-To: <CACsJy8D7+sXF9gRj15kidgK_xzSVHqChSFdqHpJ3PwxMOw2rHA@mail.gmail.com>
Hi Duy,
On Thu, 10 Mar 2016, Duy Nguyen wrote:
> On Thu, Mar 10, 2016 at 6:51 PM, Duy Nguyen <pclouds@gmail.com> wrote:
> >> It gets rather tiresome, and also typo-prone, to call "git branch xyz
> >> upstream/master && git worktree add xyz xyz" all the time.
> >
> > You can actually do "git worktree -b xyz xyz upstream/master" for the
> > same effect. Maybe we can avoid "xyz" duplication with "-b -" or a new
> > option name?
>
> Another option is just do "worktree -b xyz . upstream/master"
>
> when the destination already exists and is a directory, the real
> worktree location is <dest>/<branch name>. Similar to "mv abc def"
> becomes "mv abc def/abc" when def is already a directory.
Hmm. That sounds too clever to me. It is clever, alright, but it is also
confusing: "Wait, what? Where is my... Darn! It already existed! And now I
have my-cool-worktree/my-cool-worktree/! Blergh."
Please count that as mild opposition to that idea :-)
Ciao,
Dscho
next prev parent reply other threads:[~2016-03-10 13:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 11:34 [PATCH 0/1] Introduce a way to create a branch and worktree at the same time Johannes Schindelin
2016-03-10 11:34 ` [PATCH 1/1] branch: allow conveniently adding new worktrees for new branches Johannes Schindelin
2016-03-10 11:51 ` [PATCH 0/1] Introduce a way to create a branch and worktree at the same time Duy Nguyen
2016-03-10 11:59 ` Duy Nguyen
2016-03-10 13:24 ` Johannes Schindelin [this message]
2016-03-10 13:21 ` Johannes Schindelin
2016-03-11 0:56 ` Duy Nguyen
2016-03-11 6:43 ` Junio C Hamano
2016-03-15 6:53 ` Johannes Schindelin
2016-03-15 10:34 ` Duy Nguyen
2016-03-15 13:56 ` Johannes Schindelin
2016-03-15 14:07 ` Duy Nguyen
2016-03-11 2:57 ` Mikael Magnusson
2016-03-14 13:45 ` Johannes Schindelin
2016-03-15 20:40 ` Johannes Sixt
2016-03-10 20:45 ` Eric Sunshine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1603101422190.4690@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).