From: Johannes Sixt <j6t@kdbg.org>
To: Mikael Magnusson <mikachu@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Duy Nguyen <pclouds@gmail.com>,
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 21:40:23 +0100 [thread overview]
Message-ID: <56E87337.3040609@kdbg.org> (raw)
In-Reply-To: <CAHYJk3Sij4tH0i29Asahjj8KBdQj59jFRTCoYzO_XE_kt3SnDw@mail.gmail.com>
Am 11.03.2016 um 03:57 schrieb Mikael Magnusson:
> You can have /usr/src/git/master, /usr/src/git/some-work-tree, etc,
> and /usr/src/git itself is not a git repository at all. That way
> /usr/src only has one git-related directory and no worktrees are
> nested.
I started using separate worktrees recently, and I chose the layout you
sketch here. I didn't ask someone or read any documentation to find out
about a recommended layout. I chose the layout because it felt the most
natural.
Never in my life would I have considered nesting worktrees inside other
worktrees.
-- Hannes
next prev parent reply other threads:[~2016-03-15 20:40 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
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 [this message]
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=56E87337.3040609@kdbg.org \
--to=j6t@kdbg.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mikachu@gmail.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).