Re: [PATCH v4 0/1] receive-pack: optionally deny case clone refs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Torsten Bögershausen <tboegi@xxxxxx> writes:

> Or try to have a functionality to always use packed refs, and have a configuration
> for it:
>
> The advantage can be that branch names like "Branch" and "BRANCH" can live together
> in a project, regardless if you have a case sensitive or insensitve file system.

That is unfortunately *FALSE*.  You forgot about how reflogs are
stored for these branches.

> Another advantage with the "always packed refs" is that you can have branches
> bugfix and bugfix/next-bug side by side.

Again, you forgot about reflogs.

For this case I do not think it even is unfortunate.  Having two
"bugfix" and "bugfix/a" branches, if you are planning to use the
hierarchical names to group things together, does not make much
sense, and if you are not using these hierarchical names to group
things together you can always use "bugfix" vs "bugfix-a" instead.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]