git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Elijah Newren <newren@gmail.com>
Cc: Chris Torek <chris.torek@gmail.com>,
	Craig H Maynard <chmaynard@me.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Regarding Git and Branch Naming
Date: Fri, 26 Jun 2020 23:14:12 -0400	[thread overview]
Message-ID: <20200627031412.GC1187031@coredump.intra.peff.net> (raw)
In-Reply-To: <CABPp-BE7y5YD4A+QTn-2Vu5aS8c_pzQ2096Y7GRqeOOSJKwJHQ@mail.gmail.com>

On Fri, Jun 26, 2020 at 02:58:17PM -0700, Elijah Newren wrote:

> The error doesn't need to come that late; it could come at the "init"
> step when no branch name is specified.  If that's desirable, a
> necessary first step towards that would be making a plain "git init"
> throw a warning that we are creating a repo with a default branch name
> of <whatever> since the user didn't specify one.
> 
> Of course, we could decide to only take that first step and never
> escalate it to an error.  It'd still leave us with some default name,
> but would de-emphasize it some.
> 
> Not sure if I'm in favor of either of these ideas or not, but just
> thought I'd point out alternate possibilities towards
> removing/de-emphasizing the default initial branch name.

Yeah, I agree those are all possible options. My issue is that not
picking a default means the user is forced to do so before continuing,
which seems fundamentally unfriendly to me. It's putting more friction
between the user and their goal.

The warning version doesn't force that choice, but then I don't think
that's it really accomplished that much. We've still got to have a
default, and now we have an annoying warning on top. :)

-Peff

      reply	other threads:[~2020-06-27  3:14 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
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 [this message]

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=20200627031412.GC1187031@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=chmaynard@me.com \
    --cc=chris.torek@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.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).