From: Junio C Hamano <gitster@pobox.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, newren@gmail.com, peff@peff.net, sbeller@google.com
Subject: Re: [PATCH v3 2/8] Add a place for (not) sharing stuff between worktrees
Date: Mon, 22 Oct 2018 13:28:41 +0900 [thread overview]
Message-ID: <xmqqin1uwqo6.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20181021080859.3203-3-pclouds@gmail.com> ("Nguyễn Thái Ngọc Duy"'s message of "Sun, 21 Oct 2018 10:08:53 +0200")
Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:
> Subject: Re: [PATCH v3 2/8] Add a place for (not) sharing stuff between worktrees
"a place"? Missing "in $GIR_DIR" in the descrition made me read the
above three times before getting what it wanted to say.
My attempt to improve it, which admittedly is not great, came up with:
worktree: convention to make per-worktree things identifiable in $GIT_DIR
> When multiple worktrees are used, we need rules to determine if
> something belongs to one worktree or all of them. Instead of keeping
> adding rules when new stuff comes (*), have a generic rule:
>
> - Inside $GIT_DIR, which is per-worktree by default, add
> $GIT_DIR/common which is always shared. New features that want to
> share stuff should put stuff under this directory.
>
> - Inside refs/, which is shared by default except refs/bisect, add
> refs/worktree/ which is per-worktree. We may eventually move
> refs/bisect to this new location and remove the exception in refs
> code.
>
> (*) And it may also include stuff from external commands which will
> have no way to modify common/per-worktree rules.
OK. Establishing such a convention is a good role for the core-git
should play to help third-party tools.
Should this play well with the per-worktree configuration as well?
Is it better to carve out a configuration variable namespace so that
certain keys are never read from common ones (or per-worktree ones),
so that people can tell which ones are what? I know your current
design says "this is just another new layer, and the users can hang
themselves with this new rope". I am wondering if there is a need
to do something a bit more structured.
next prev parent reply other threads:[~2018-10-22 4:28 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 18:04 [PATCH 0/8] fix per-worktree ref iteration in fsck/reflog expire Nguyễn Thái Ngọc Duy
2018-09-22 18:04 ` [PATCH 1/8] refs.c: indent with tabs, not spaces Nguyễn Thái Ngọc Duy
2018-09-22 18:04 ` [PATCH 2/8] Add a place for (not) sharing stuff between worktrees Nguyễn Thái Ngọc Duy
2018-09-23 7:51 ` Eric Sunshine
2018-09-25 2:35 ` Stefan Beller
2018-09-25 15:36 ` Duy Nguyen
2018-09-25 16:24 ` Stefan Beller
2018-09-25 16:55 ` Duy Nguyen
2018-09-25 17:56 ` Stefan Beller
2018-09-22 18:04 ` [PATCH 3/8] refs: new ref types to make per-worktree refs visible to all worktrees Nguyễn Thái Ngọc Duy
2018-09-23 8:06 ` Eric Sunshine
2018-09-23 13:10 ` Duy Nguyen
2018-09-25 2:48 ` Stefan Beller
2018-09-25 15:49 ` Duy Nguyen
2018-09-25 16:53 ` Stefan Beller
2018-09-25 21:16 ` Junio C Hamano
2018-09-29 18:26 ` Duy Nguyen
2018-10-06 23:20 ` Junio C Hamano
2018-09-22 18:04 ` [PATCH 4/8] revision.c: correct a parameter name Nguyễn Thái Ngọc Duy
2018-09-22 18:04 ` [PATCH 5/8] revision.c: better error reporting on ref from different worktrees Nguyễn Thái Ngọc Duy
2018-09-23 8:25 ` Eric Sunshine
2018-09-23 13:15 ` Duy Nguyen
2018-09-22 18:04 ` [PATCH 6/8] fsck: Move fsck_head_link() to get_default_heads() to avoid some globals Nguyễn Thái Ngọc Duy
2018-09-22 18:04 ` [PATCH 7/8] fsck: check HEAD and reflog from other worktrees Nguyễn Thái Ngọc Duy
2018-09-23 8:41 ` Eric Sunshine
2018-09-29 18:40 ` Duy Nguyen
2018-09-22 18:05 ` [PATCH 8/8] reflog expire: cover reflog from all worktrees Nguyễn Thái Ngọc Duy
2018-09-29 19:10 ` [PATCH v2 0/8] fix per-worktree ref iteration in fsck/reflog expire Nguyễn Thái Ngọc Duy
2018-09-29 19:10 ` [PATCH v2 1/8] refs.c: indent with tabs, not spaces Nguyễn Thái Ngọc Duy
2018-09-29 19:10 ` [PATCH v2 2/8] Add a place for (not) sharing stuff between worktrees Nguyễn Thái Ngọc Duy
2018-09-29 19:10 ` [PATCH v2 3/8] refs: new ref types to make per-worktree refs visible to all worktrees Nguyễn Thái Ngọc Duy
2018-09-30 5:13 ` Eric Sunshine
2018-10-07 1:37 ` Junio C Hamano
2018-09-29 19:10 ` [PATCH v2 4/8] revision.c: correct a parameter name Nguyễn Thái Ngọc Duy
2018-09-29 19:10 ` [PATCH v2 5/8] revision.c: better error reporting on ref from different worktrees Nguyễn Thái Ngọc Duy
2018-09-30 5:25 ` Eric Sunshine
2018-09-29 19:10 ` [PATCH v2 6/8] fsck: Move fsck_head_link() to get_default_heads() to avoid some globals Nguyễn Thái Ngọc Duy
2018-09-29 19:10 ` [PATCH v2 7/8] fsck: check HEAD and reflog from other worktrees Nguyễn Thái Ngọc Duy
2018-09-29 19:10 ` [PATCH v2 8/8] reflog expire: cover reflog from all worktrees Nguyễn Thái Ngọc Duy
2018-09-30 5:36 ` Eric Sunshine
2018-10-02 16:16 ` Duy Nguyen
2018-10-03 7:49 ` Eric Sunshine
2018-10-21 8:08 ` [PATCH v3 0/8] fix per-worktree ref iteration in fsck/reflog expire Nguyễn Thái Ngọc Duy
2018-10-21 8:08 ` [PATCH v3 1/8] refs.c: indent with tabs, not spaces Nguyễn Thái Ngọc Duy
2018-10-21 8:08 ` [PATCH v3 2/8] Add a place for (not) sharing stuff between worktrees Nguyễn Thái Ngọc Duy
2018-10-22 4:28 ` Junio C Hamano [this message]
2018-10-29 17:18 ` Duy Nguyen
2018-10-22 10:25 ` SZEDER Gábor
2018-10-21 8:08 ` [PATCH v3 3/8] refs: new ref types to make per-worktree refs visible to all worktrees Nguyễn Thái Ngọc Duy
2018-11-24 19:27 ` Ævar Arnfjörð Bjarmason
2018-11-25 1:19 ` Junio C Hamano
2018-11-25 4:58 ` [PATCH] files-backend.c: fix build error on Solaris Nguyễn Thái Ngọc Duy
2018-11-25 10:19 ` Carlo Arenas
2018-11-25 10:40 ` Duy Nguyen
2018-11-26 4:44 ` Junio C Hamano
2018-10-21 8:08 ` [PATCH v3 4/8] revision.c: correct a parameter name Nguyễn Thái Ngọc Duy
2018-10-21 8:08 ` [PATCH v3 5/8] revision.c: better error reporting on ref from different worktrees Nguyễn Thái Ngọc Duy
2018-10-21 8:08 ` [PATCH v3 6/8] fsck: Move fsck_head_link() to get_default_heads() to avoid some globals Nguyễn Thái Ngọc Duy
2018-10-21 8:08 ` [PATCH v3 7/8] fsck: check HEAD and reflog from other worktrees Nguyễn Thái Ngọc Duy
2018-10-21 8:08 ` [PATCH v3 8/8] reflog expire: cover reflog from all worktrees Nguyễn Thái Ngọc Duy
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqin1uwqo6.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).