From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Jacob Keller <jacob.keller@gmail.com>,
Git mailing list <git@vger.kernel.org>, Eric Wong <e@80x24.org>
Subject: Re: avoiding fetching specific refs from a remote
Date: Wed, 5 Aug 2020 18:12:42 -0400 [thread overview]
Message-ID: <BE29FA64-5281-4D9E-B509-CA2C2B7BB87D@gmail.com> (raw)
In-Reply-To: <20200805063704.GA2690083@coredump.intra.peff.net>
Hi Peff,
> Le 5 août 2020 à 02:37, Jeff King <peff@peff.net> a écrit :
>
> On Tue, Aug 04, 2020 at 02:53:30PM -0700, Jacob Keller wrote:
>
>> 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.
I tried searching "negative refspecs" (*with* the double quotes) and I get 20 results so it
seems to work. Although interestingly it doesn't find this message you wrote I'm responding to
because "negative" and "refspec" are on separate lines... I'm CC-ing Eric in case he knows more
about this limitation.
Philippe.
next prev parent reply other threads:[~2020-08-05 22:13 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
2020-08-05 20:31 ` Jacob Keller
2020-08-05 22:12 ` Philippe Blain [this message]
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=BE29FA64-5281-4D9E-B509-CA2C2B7BB87D@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=peff@peff.net \
/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).