From: Jacob Keller <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: Jeff King <email@example.com>, Git mailing list <firstname.lastname@example.org> Subject: Re: avoiding fetching specific refs from a remote Date: Wed, 5 Aug 2020 13:34:08 -0700 [thread overview] Message-ID: <CA+P7+xrAyCgYyh4_WM5hcBv8+WXaRvN_Cf6nqz4ruO4oHzwjvQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Wed, Aug 5, 2020 at 9:22 AM Junio C Hamano <firstname.lastname@example.org> wrote: > > Jeff King <email@example.com> 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://firstname.lastname@example.org/ > Right. I'm generally for the name change, and I like having the remote honor the old name as a compatibility at least for some duration. > > 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. > > I think the idea is interesting. I sometimes find negative > pathspecs quite useful, and I suspect negative refspecs would also > be. I've found negative pathspecs incredibly useful in some contexts, (with my only issue being to remember that if you specify a negative pathspec, you must also specify a positive one i.e. "." or something) I think I'll try to revive that one patch Peff pointed out and then see if it makes sense or needs to be redone.
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 Jacob Keller 2020-08-05 6:37 ` Jeff King 2020-08-05 16:22 ` Junio C Hamano 2020-08-05 20:34 ` Jacob Keller [this message] 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 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=CA+P7+xrAyCgYyh4_WM5hcBv8+WXaRvN_Cf6nqz4ruO4oHzwjvQ@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: avoiding fetching specific refs from a remote' \ /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
Code repositories for project(s) associated with this 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).