From: "brian m. carlson" <firstname.lastname@example.org> To: Mike Rappazzo <email@example.com> Cc: "Stefan Beller" <firstname.lastname@example.org>, "Nguyễn Thái Ngọc" <email@example.com>, firstname.lastname@example.org, "Git List" <email@example.com>, "Junio C Hamano" <firstname.lastname@example.org> Subject: Re: [PATCH 1/1] worktree refs: fix case sensitivity for 'head' Date: Fri, 14 Dec 2018 00:33:51 +0000 [thread overview] Message-ID: <20181214003350.GS890086@genre.crustytoothpaste.net> (raw) In-Reply-To: <CANoM8SWQTAEYGiUC9PnWi8u9oAJYPcyiE5+5usoRvR7Vw2z0JA@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1185 bytes --] On Thu, Dec 13, 2018 at 04:14:28PM -0500, Mike Rappazzo wrote: > On Thu, Dec 13, 2018 at 3:48 PM Stefan Beller <email@example.com> wrote: > > > > > > The current situation is definitely a problem. If I am in a worktree, > > > > using "head" should be the same as "HEAD". > > > > By any chance, is your file system case insensitive? > > That is usually the source of confusion for these discussions. > > This behavior is the same for MacOS (High Sierra) and Windows 7. I > assume other derivatives of those act the same. > > On CentOS "head" is an ambiguous ref. If Windows and Mac resulted in > an ambiguous ref, that would also be OK, but as it is now, they return > the result of "HEAD" on the primary worktree. I'm pretty sure that we want HEAD to be only written as "HEAD". It's known that systems with case-insensitive file systems sometimes allow "head" instead of "HEAD" because the ref is written in the file system. I think the improvement we'd want here is to reject HEAD being written as "head" on those systems, but in a global way that affects all uses of HEAD. -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2018-12-14 0:33 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-13 19:54 [PATCH 0/1] " 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 [this message] 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=20181214003350.GS890086@genre.crustytoothpaste.net \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 1/1] worktree refs: fix case sensitivity for '\''head'\''' \ /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
Code repositories for project(s) associated with this 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).