From: "Michael Rappazzo via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] worktree refs: fix case sensitivity for 'head'
Date: Thu, 13 Dec 2018 11:54:10 -0800 (PST) [thread overview]
Message-ID: <pull.100.git.gitgitgadget@gmail.com> (raw)
On a worktree which is not the primary, using the symbolic-ref 'head' was
incorrectly pointing to the main worktree's HEAD. The same was true for any
other casing of the word 'Head'.
Signed-off-by: Michael Rappazzo rappazzo@gmail.com [rappazzo@gmail.com]
Michael Rappazzo (1):
worktree refs: fix case sensitivity for 'head'
refs.c | 8 ++++----
t/t1415-worktree-refs.sh | 9 +++++++++
2 files changed, 13 insertions(+), 4 deletions(-)
base-commit: 5d826e972970a784bd7a7bdf587512510097b8c7
Published-As: https://github.com/gitgitgadget/git/releases/tags/pr-100%2Frappazzo%2Fhead_case_sensitivity_on_worktree-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-100/rappazzo/head_case_sensitivity_on_worktree-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/100
--
gitgitgadget
next reply other threads:[~2018-12-13 19:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 19:54 Michael Rappazzo via GitGitGadget [this message]
2018-12-13 19:54 ` [PATCH 1/1] worktree refs: fix case sensitivity for 'head' Michael Rappazzo via GitGitGadget
2018-12-13 20:23 ` Duy Nguyen
2018-12-13 20:34 ` Mike Rappazzo
2018-12-13 20:43 ` Duy Nguyen
2018-12-13 20:47 ` Stefan Beller
2018-12-13 21:14 ` Mike Rappazzo
2018-12-14 0:33 ` brian m. carlson
2018-12-14 6:49 ` Jacob Keller
2018-12-14 7:37 ` Duy Nguyen
2018-12-14 17:22 ` Jacob Keller
2018-12-14 17:38 ` Duy Nguyen
2018-12-14 17:46 ` Duy Nguyen
2018-12-14 18:48 ` Jacob Keller
2018-12-14 18:47 ` Jacob Keller
2018-12-13 21:07 ` Mike Rappazzo
2018-12-14 3:31 ` Junio C Hamano
2018-12-14 10:36 ` [PATCH 0/1] " Johannes Schindelin
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=pull.100.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--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.
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).