git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 17:29 UTC

Re: [PATCH] Disallow creating ambiguous branch names by default

From
Conrad Irwin <conrad.irwin@gmail.com>
Date
Aug 19, 2011, 18:07 UTC
Message-ID
<CAOTq_ptdf3NvoeQXzdABdnU50w1ZwL=wnF6rPJvZpnqcU64-+g@mail.gmail.com>
In-Reply-To
<14776204.81375.1313675595871.JavaMail.root@mail.hq.genarts.com>
On Thu, Aug 18, 2011 at 6:53 AM, Stephen Bash <bash@genarts.com> wrote:
>
> Should case insensitive matches be added to the tests?  This morning I discovered coworkers working on branches foo and Foo thinking they were on the same branch...  Rather trivial to clean up, but certainly caused some confusion in the office.
>

I can certainly see the use-case, but there's definitely a step-change between "this branch has the same name as something else", and "this branch is going to confuse you". When trying to change the code to be a warning as Junio suggested, I did think about expanding the definition of ambiguous to include things that are merely confusing; however it's not clear where to stop (i.e. should we warn about <remotename>/<anything>, foo and f00, a branch called " " [the non-breaking space]). There's probably an argument for more general warning, but I don't think I understand when it should be shown well-enough.

Conrad
Previous: Stephen BashNext: Conrad Irwin
Message 5 of 10 in “Disallow creating ambiguous branch names by default”
  1. Disallow creating ambiguous branch names by defaultConrad Irwin, Aug 17, 2011
  2. Junio C HamanoAug 17, 2011
  3. Vijay LakshminarayananAug 18, 2011
  4. Stephen BashAug 18, 2011
  5. Conrad IrwinAug 19, 2011
  6. Conrad IrwinAug 19, 2011
  7. Stephen BashAug 19, 2011
  8. Junio C HamanoAug 19, 2011
  9. Conrad IrwinAug 19, 2011
  10. Junio C HamanoAug 19, 2011

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.