From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Mike Rappazzo <rappazzo@gmail.com>,
gitgitgadget@gmail.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 1/1] worktree refs: fix case sensitivity for 'head'
Date: Fri, 14 Dec 2018 12:31:35 +0900 [thread overview]
Message-ID: <xmqqefakdbs8.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACsJy8Bj=8xHp3JA8dLbyM=RwJey7utMK6DTVe_0AjBNVHxJyg@mail.gmail.com> (Duy Nguyen's message of "Thu, 13 Dec 2018 21:43:11 +0100")
Duy Nguyen <pclouds@gmail.com> writes:
> If you make "head" work like "HEAD", then it should work for _all_
> commands, not just worktree, and "MASTER" should match
> "refs/heads/master" and so on. I don't think it's as simple as
> changing strcmp to strcasecmp. You would need to make ref management
> case-insensitive (and make sure if still is case-sensitive if
> configured so). I don't think anybody has managed that.
And it is unclear why anybody would even want to do so.
Thanks for a doze of sanity.
next prev parent reply other threads:[~2018-12-14 3:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 19:54 [PATCH 0/1] worktree refs: fix case sensitivity for 'head' Michael Rappazzo via GitGitGadget
2018-12-13 19:54 ` [PATCH 1/1] " 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 [this message]
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=xmqqefakdbs8.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=pclouds@gmail.com \
--cc=rappazzo@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).