From: Jeff King <peff@peff.net>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: avoiding fetching specific refs from a remote
Date: Wed, 5 Aug 2020 02:37:04 -0400 [thread overview]
Message-ID: <20200805063704.GA2690083@coredump.intra.peff.net> (raw)
In-Reply-To: <CA+P7+xpokJ3Z4xZ9ibCBpBO65D1v-AD6_JknprGUsEDxEvMGGw@mail.gmail.com>
On Tue, Aug 04, 2020 at 02:53:30PM -0700, Jacob Keller wrote:
> This results in the annoying completion behavior where:
>
> $git checkout ma<TAB>
> main
> master
>
> 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.
> I'd like to be able to customize my pull so that I either (a) exclude
> the reference when performing a fetch, or (b) exclude the reference
> when tab completing.
Not quite (b), but if you:
- delete any local "master" branch, if you haven't already
- set $GIT_COMPLETION_CHECKOUT_NO_GUESS to "1"
then it shouldn't complete "master". The second is necessary because
we'd try to complete the magic "git checkout master" that auto-creates
the branch from the remote version.
> something like adding a remote.<name>.excludeRefs which would allow
> specifying a set of references to exclude from matching the refspec..
>
> I realize I could customize the refspec to list the set of things I
> want, but then I would miss any potential future branches until I
> updated my remote config again.
This is definitely a reasonable thing to want, and it has come up off
and on over the years. One search term for the list archive is "negative
refspecs", though it turns up a lot of useless hits when the two words
are not directly adjacent.
This old thread might be worth reading:
https://lore.kernel.org/git/20140124090104.GA396@x4/
and there is even a patch in there:
https://lore.kernel.org/git/20140125013433.GA22336@sigill.intra.peff.net/
but I didn't go over it carefully enough to know whether it is utter
trash, or something that could be used as a starting point.
-Peff
next prev parent reply other threads:[~2020-08-05 6:37 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 [this message]
2020-08-05 16:22 ` Junio C Hamano
2020-08-05 20:34 ` Jacob Keller
2020-08-05 20:34 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200805063704.GA2690083@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--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.
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 NNTP newsgroup(s).