On Tue, 2014-06-03 at 15:13 -0700, Junio C Hamano wrote:
> David Turner writes:
>
> > I would be happy to add "case-clone" to the glossary -- would that be OK
> > with you? I do not immediately think of the better term.
>
> Somehow "case-clone" sounds strange, though X-<.
Case clones case clon
David Turner writes:
> I would be happy to add "case-clone" to the glossary -- would that be OK
> with you? I do not immediately think of the better term.
Somehow "case-clone" sounds strange, though X-<.
>> (Mental note to the reviewer himself) This returns true iff there is
>> an existing ref
On Tue, 2014-06-03 at 14:33 -0700, Junio C Hamano wrote:
> David Turner writes:
>
> > It is possible to have two branches which are the same but for case.
> > This works great on the case-sensitive filesystems, but not so well on
> > case-insensitive filesystems. It is fairly typical to have
> >
David Turner writes:
> It is possible to have two branches which are the same but for case.
> This works great on the case-sensitive filesystems, but not so well on
> case-insensitive filesystems. It is fairly typical to have
> case-insensitive clients (Macs, say) with a case-sensitive server
>
It is possible to have two branches which are the same but for case.
This works great on the case-sensitive filesystems, but not so well on
case-insensitive filesystems. It is fairly typical to have
case-insensitive clients (Macs, say) with a case-sensitive server
(GNU/Linux).
Should a user attem
5 matches
Mail list logo
