From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: wchargin@gmail.com, Git Mailing List <git@vger.kernel.org>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH] sha1-name.c: for ":/", find detached HEAD commits
Date: Wed, 11 Jul 2018 10:20:54 -0700 [thread overview]
Message-ID: <xmqqfu0p3czt.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACsJy8CBJvpKAAtVjrdcuO06WossxcMmqwmSRL9Shr7g+qVySA@mail.gmail.com> (Duy Nguyen's message of "Wed, 11 Jul 2018 17:45:09 +0200")
Duy Nguyen <pclouds@gmail.com> writes:
>> diff --git a/sha1-name.c b/sha1-name.c
>> index 60d9ef3c7..641ca12f9 100644
>> --- a/sha1-name.c
>> +++ b/sha1-name.c
>> @@ -1650,6 +1650,7 @@ static int get_oid_with_context_1(const char *name,
>> struct commit_list *list = NULL;
>>
>> for_each_ref(handle_one_ref, &list);
>> + head_ref(handle_one_ref, &list);
>
> When multiple worktrees are used, should we consider all HEADs or just
> current worktree's HEAD?
Does for_each_ref() iterate over per-worktree refs (like "bisect",
perhaps)? If so, then looking in different worktree's HEADs would
make sense, and otherwise not.
I would think that the whole point of detaching HEAD in a separate
worktree is that you can avoid exposing the work you do while
detached to other worktrees by doing so, so from that point of view,
I would probably prefer :/ not to look into other worktrees, but
that is not a very strong preference. If peeking all over the place
is easier to implement, then a minor information leaking is not
something I'd lose sleep over.
Thanks for bringing up an interesting issue.
next prev parent reply other threads:[~2018-07-11 17:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 15:41 [PATCH] sha1-name.c: for ":/", find detached HEAD commits William Chargin
2018-07-10 17:54 ` Jeff King
2018-07-10 19:06 ` Junio C Hamano
2018-07-11 6:18 ` William Chargin
2018-07-11 12:32 ` Jeff King
2018-07-11 16:34 ` Junio C Hamano
2018-07-11 15:45 ` Duy Nguyen
2018-07-11 16:40 ` Jeff King
2018-07-11 17:20 ` Junio C Hamano [this message]
2018-07-11 17:37 ` Duy Nguyen
2018-07-11 17:49 ` William Chargin
2018-07-12 5:49 ` [PATCH v2] " William Chargin
2018-07-12 15:49 ` Jeff King
2018-07-12 16:04 ` Junio C Hamano
2018-07-12 16:14 ` William Chargin
2018-07-12 19:09 ` Junio C Hamano
2018-07-12 20:01 ` William Chargin
2018-07-13 19:24 ` Jeff King
2018-07-13 19:40 ` William Chargin
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=xmqqfu0p3czt.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=wchargin@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.
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).