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

Re: Minor Bug in Renaming Branches

From
Stefan Beller <sbeller@google.com>
Date
Jun 6, 2016, 18:09 UTC
Message-ID
<CAGZ79kZg_ZjBS4gB+P68J+mpzGqkPNW+5NdrRiHmA0uC235RBQ@mail.gmail.com>
In-Reply-To
<CA+wHs3MSax1eo9V_5hnsbEte0k5tX22dAgSUAEzN7aw22rUnhA@mail.gmail.com>
On Mon, Jun 6, 2016 at 10:52 AM, Samuel Lijin <samuel.lijin@formlabs.com> wrote:
> user@windows-box MINGW64 ~/sandbox (branch/name)
> $ git branch -m BRANCH/NAME
> fatal: A branch named 'BRANCH/NAME' already exists.

Yeah, branches/refs are treated as if they are files on a file system (which they are currently). So depending on the file system used you have problems with case sensitive things.

Previous: Samuel LijinNext: Torsten Bögershausen
Message 2 of 7 in “Minor Bug in Renaming Branches”
  1. Samuel LijinJun 6, 2016
  2. Stefan BellerJun 6, 2016
  3. Torsten BögershausenJun 6, 2016
  4. Stefan BellerJun 6, 2016
  5. Torsten BögershausenJun 7, 2016
  6. Eric DeplagneJun 7, 2016
  7. Stefan BellerJun 7, 2016

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.