From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jacob Keller <jacob.keller@gmail.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: avoiding fetching specific refs from a remote
Date: Wed, 5 Aug 2020 16:34:25 -0400 [thread overview]
Message-ID: <20200805203425.GA2706898@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq1rkloyeg.fsf@gitster.c.googlers.com>
On Wed, Aug 05, 2020 at 09:22:47AM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> >> Essentially, because both main and master have similar names, tab
> >> completion requires remembering to type one additional character than
> >> I am used to.
> >
> > Heh, I didn't think anybody considered that implication so far; the fact
> > that they were similar names has generally been considered a positive. I
> > agree it would be annoying.
>
> FWIW, I've been saying that 'maint' will become harder to type all
> along ever since I heard 'main'.
>
> https://lore.kernel.org/git/xmqqtuz9tq30.fsf@gitster.c.googlers.com/
True, but I thought that was just a reason against "main" in git.git
itself. Most repos don't have "maint" (and we already conflicted on "ma"
with the existing name :) though I agree that having one as a prefix of
the other makes completion doubly painful). The interesting bit here is
that the old name probably _isn't_ going away immediately, so this would
affect everybody.
-Peff
next prev parent reply other threads:[~2020-08-05 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 21:53 avoiding fetching specific refs from a remote Jacob Keller
2020-08-05 6:37 ` Jeff King
2020-08-05 16:22 ` Junio C Hamano
2020-08-05 20:34 ` Jacob Keller
2020-08-05 20:34 ` Jeff King [this message]
2020-08-05 20:31 ` Jacob Keller
2020-08-05 22:12 ` Philippe Blain
2020-08-07 8:04 ` Eric Wong
2020-08-12 22:04 ` Jacob Keller
2020-08-13 8:48 ` 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=20200805203425.GA2706898@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@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).