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, 19:35 UTC
Message-ID
<CAGZ79kb77m8ymDkJGMaWi8yOdSphpYifDPHQ=+nZMBhRi47i9w@mail.gmail.com>
In-Reply-To
<54505ef2-7db6-8bc4-0ffb-0ac28c7d6046@web.de>
On Mon, Jun 6, 2016 at 12:17 PM, Torsten Bögershausen <tboegi@web.de> wrote:
Show 5 quoted lines
> A limitation is introduced by Mac OS and Windows:
> BRANCH/NAME and branch/name refer to the same object in the file
> system.
> As a workaround, you can pack the branch names:
> git pack-refs --all

Once you packed a branch into the packed refs file, you can create another loose branch of different capitalization, which then 'hides' the packed ref?

That sounds error prone to me, as a seemingly unrelated branch changed its value:

    git branch BRANCH 012345
    git pack-refs --all
    git branch branch BRANCH^
    git rev-parse BRANCH
    (I'd expect BRANCH^ as return)

(I don't have a windows machine for testing here, so that is pure speculation)

Thanks, Stefan

Previous: Torsten BögershausenNext: Torsten Bögershausen
Message 4 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.