From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: David Turner <dturner@twopensource.com>,
git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>,
Ronnie Sahlberg <sahlberg@google.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCH v4 0/1] receive-pack: optionally deny case clone refs
Date: Fri, 13 Jun 2014 10:12:56 -0700 [thread overview]
Message-ID: <xmqq38f84tt3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <539A7821.906@web.de> ("Torsten Bögershausen"'s message of "Fri, 13 Jun 2014 06:03:45 +0200")
Torsten Bögershausen <tboegi@web.de> 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.
next prev parent reply other threads:[~2014-06-13 17:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 22:30 [PATCH v4 0/1] receive-pack: optionally deny case clone refs David Turner
2014-06-11 22:30 ` [PATCH v4 1/1] " David Turner
2014-06-13 4:03 ` Torsten Bögershausen
2014-06-12 19:47 ` [PATCH v4 0/1] " Junio C Hamano
2014-06-12 23:30 ` David Turner
2014-06-13 4:03 ` Torsten Bögershausen
2014-06-13 17:12 ` Junio C Hamano [this message]
2014-06-13 17:08 ` Junio C Hamano
2014-06-13 18:20 ` Ronnie Sahlberg
2014-06-13 19:05 ` Ronnie Sahlberg
2014-06-13 21:11 ` Junio C Hamano
2014-06-13 22:24 ` Ronnie Sahlberg
2014-06-15 7:10 ` David Turner
2014-06-13 21:25 ` Junio C Hamano
2014-06-18 11:33 ` Michael Haggerty
2014-06-18 15:03 ` Ronnie Sahlberg
2014-08-13 16:20 ` Ronnie Sahlberg
2014-08-13 19:28 ` David Turner
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=xmqq38f84tt3.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=sahlberg@google.com \
--cc=tboegi@web.de \
/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.