All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
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: Tue, 15 Mar 2016 17:34:37 +0700	[thread overview]
Message-ID: <CACsJy8B+c8=Y0Lb-TxjGF4689xP2Vyqjp4Q6CuffTLDWDMh3gg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1603150746490.4690@virtualbox>

On Tue, Mar 15, 2016 at 1:53 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>> 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.

I disagree (unless I misunderstood you). One of the use cases I have
for multi worktree is move all repos to a central place. Remember the
.git directory security bug? It would not happen if the repo is put
away. And it would be easier to backup repo data too. Also, "git
worktree list" is there to locate any worktree. I don't see why it's
confusing.
-- 
Duy

  reply	other threads:[~2016-03-15 10:35 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
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 [this message]
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='CACsJy8B+c8=Y0Lb-TxjGF4689xP2Vyqjp4Q6CuffTLDWDMh3gg@mail.gmail.com' \
    --to=pclouds@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.