From: Junio C Hamano <gitster@pobox.com>
To: David Turner <dturner@twopensource.com>
Cc: git@vger.kernel.org, sunshine@sunshineco.com
Subject: Re: [PATCH v2] notes: handle multiple worktrees
Date: Fri, 31 Jul 2015 15:00:48 -0700 [thread overview]
Message-ID: <xmqqmvyc3s33.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1438379086.4735.25.camel@twopensource.com> (David Turner's message of "Fri, 31 Jul 2015 17:44:46 -0400")
David Turner <dturner@twopensource.com> writes:
> I further propose to add some patches (to go on top of the pseudorefs
> series):
>
> (a) include worktree-refs/ in per_worktree_refs and include
> worktree-refs/ in per_worktree_refs in common_list, and
Do you mean .git/worktree-refs/, just next to .git/refs? Then I
think it makes sense.
> (b) include changes to bisect which switches it over to use
> worktree_refs/*. To make this change compatible with bisections started
> with old git versions,...
I personally am not sure if it is worth the effort to cater to those
who start bisection, stop and then upgrade their git version and
expect to continue.
prev parent reply other threads:[~2015-07-31 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 17:44 [PATCH v2] notes: handle multiple worktrees David Turner
2015-07-31 18:46 ` Junio C Hamano
2015-07-31 21:44 ` David Turner
2015-07-31 22:00 ` Junio C Hamano [this message]
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=xmqqmvyc3s33.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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