git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC: optionally reject case-clone branch names

From
Junio C Hamano <gitster@pobox.com>
Date
May 28, 2014, 17:14 UTC
Message-ID
<xmqq7g55esg5.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1401231368.18134.63.camel@stross>
David Turner <dturner@twopensource.com> writes:
Show 9 quoted lines
> RFC follows:
>
> 1. On a case-insensitive server, git receive-pack ought to always reject
> branches which are same-but-for-case of existing branches.
> 2. On a case-sensitive server, the same rule by default, with an option
> to allow the old behavior.
>
> Let me know if, should I write these patches, they would be likely to be
> accepted.
There is another a lot simpler possiblity, no?
3. On any server whose administrator chooses to enforce "one case
   variant only" rule, install a pre-receive hook that enforces the
   rule.
Previous: David TurnerNext: David Turner
Message 2 of 4 in “RFC: optionally reject case-clone branch names”
  1. David TurnerMay 27, 2014
  2. Junio C HamanoMay 28, 2014
  3. David TurnerMay 28, 2014
  4. Junio C HamanoMay 28, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.