On Tue, Jun 7, 2016 at 12:40 AM, Eric Deplagne wrote:
> 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 wrote:
>>>
A limitation is introduced by Mac OS and Windows:
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 wrote:
>>
>>> A limitation is introduced by Mac OS and Windows:
>>> BRANCH/NAME and branch/name refer to the same object in the fi
On 06/06/2016 09:35 PM, Stefan Beller wrote:
On Mon, Jun 6, 2016 at 12:17 PM, Torsten Bögershausen 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 --a
On Mon, Jun 6, 2016 at 12:17 PM, Torsten Bögershausen 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
On 06.06.16 19:52, Samuel Lijin wrote:
> Hi,
>
> Not quite sure where to submit bug reports about Git, this was the
> best I could find, so if there's a better place to do this, please let
> me know and I will.
>
> The short of this issue is that on Mac and Windows, if a branch has a
> slash in i
On Mon, Jun 6, 2016 at 10:52 AM, Samuel Lijin 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 dependin
6 matches
Mail list logo
