From: "Torsten Bögershausen" <tboegi@web.de>
To: "Stefan Beller" <sbeller@google.com>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: Samuel Lijin <samuel.lijin@formlabs.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Minor Bug in Renaming Branches
Date: Tue, 7 Jun 2016 06:13:14 +0200 [thread overview]
Message-ID: <575649DA.4080702@web.de> (raw)
In-Reply-To: <CAGZ79kb77m8ymDkJGMaWi8yOdSphpYifDPHQ=+nZMBhRi47i9w@mail.gmail.com>
On 06/06/2016 09:35 PM, Stefan Beller wrote:
> On Mon, Jun 6, 2016 at 12:17 PM, Torsten Bögershausen <tboegi@web.de> 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)
next prev parent reply other threads:[~2016-06-07 4:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 17:52 Minor Bug in Renaming Branches Samuel Lijin
2016-06-06 18:09 ` Stefan Beller
2016-06-06 19:17 ` Torsten Bögershausen
2016-06-06 19:35 ` Stefan Beller
2016-06-07 4:13 ` Torsten Bögershausen [this message]
2016-06-07 7:40 ` Eric Deplagne
2016-06-07 13:09 ` Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=575649DA.4080702@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=samuel.lijin@formlabs.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.