On Tue, 07 Jun 2016 06:13:14 +0200, Torsten Bögershausen wrote: > On 06/06/2016 09:35 PM, Stefan Beller wrote: >> On Mon, Jun 6, 2016 at 12:17 PM, Torsten Bögershausen <[email protected]> wrote: >> >>> 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) >> > Yes, another reason not to use branch and BRANCH in the same repo. > (You can test under Linux & vfat)
Or to have git just refuse it altogether... But let me guess, it's against some sort of policy... There could be some hook out there, then ? -- Eric Deplagne
signature.asc
Description: Digital signature
