From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Chris Torek <chris.torek@gmail.com>,
Craig H Maynard <chmaynard@me.com>,
git@vger.kernel.org
Subject: Re: Regarding Git and Branch Naming
Date: Fri, 26 Jun 2020 23:05:32 -0400 [thread overview]
Message-ID: <20200627030532.GA1187031@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq7dvth6xy.fsf@gitster.c.googlers.com>
On Fri, Jun 26, 2020 at 02:07:37PM -0700, Junio C Hamano wrote:
> > $ git init
> > $ git add some-files
> > $ git commit -m whatever
> > fatal: HEAD does not point to any branch
> > hint: use "git checkout -b <branch>" to make commits on <branch>
>
> ... or you could stay forever on detached HEAD state.
>
> Very briefly in early days of Git, the envisioned use case (which
> quickly was retracted) was to use one repository per one line of
> development (so you'd pull among the repositories you have, and each
> repository does not even need to have "the default" branch---there
> was no need for any branch). Staying forever on detached HEAD is
> pretty much in line with that.
Given the difficulties many users seem to have with understanding
detached HEADs, I think that might be even more unfriendly. :)
> > Perhaps that's not _too_ bad, but it feels a bit unfriendly (and
> > definitely more likely to cause backwards compatibility issues than
> > picking _some_ default name). There would also be a lot of corner cases
> > to cover and debug (e.g., "git checkout foo" moving away from the "no
> > branch" state should make the usual complaints if we'd have to overwrite
> > or modify index and untracked files).
>
> I do not see much point in adding such a new set-up, only to risk
> introducing unexpected and unnecessary bugs. Such extra engineering
> resource is better spent elsewhere, I would say.
Yeah, agreed.
-Peff
next prev parent reply other threads:[~2020-06-27 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 16:18 Regarding Git and Branch Naming Craig H Maynard
2020-06-26 18:33 ` Chris Torek
2020-06-26 20:35 ` Jeff King
2020-06-26 21:07 ` Junio C Hamano
2020-06-27 3:05 ` Jeff King [this message]
2020-06-26 21:33 ` Philip Oakley
2020-06-27 3:11 ` Jeff King
2020-06-26 21:58 ` Elijah Newren
2020-06-27 3:14 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200627030532.GA1187031@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chmaynard@me.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).