On Fri, 2014-06-06 at 08:37 +0700, Duy Nguyen wrote:
> On Fri, Jun 6, 2014 at 7:52 AM, David Turner wrote:
> > Create the option receive.denycaseclonerefs, which checks pushed
> > refs to ensure that they are not case clones of an existing
> > ref. This setting is turned on by default if core.ign
On Fri, Jun 6, 2014 at 7:52 AM, David Turner wrote:
> Create the option receive.denycaseclonerefs, which checks pushed
> refs to ensure that they are not case clones of an existing
> ref. This setting is turned on by default if core.ignorecase is
> set, but not otherwise.
Just thinking out loud
It is possible to have two refs 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 attempt t
3 matches
Mail list logo
