From: Eric Wong <firstname.lastname@example.org> To: Philippe Blain <email@example.com> Cc: Jeff King <firstname.lastname@example.org>, Jacob Keller <email@example.com>, firstname.lastname@example.org Subject: Re: avoiding fetching specific refs from a remote Date: Fri, 7 Aug 2020 08:04:36 +0000 [thread overview] Message-ID: <20200807080436.GA21342@dcvr> (raw) In-Reply-To: <BE29FA64-5281-4D9E-B509-CA2C2B7BB87D@gmail.com> Philippe Blain <email@example.com> wrote: > > Le 5 août 2020 à 02:37, Jeff King <firstname.lastname@example.org> a écrit : > > 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. Initially I thought it was phrase searching being disabled on lore (Xapian 1.2, "chert" backend). However, I just tried on lore and it shows Jeff's message from 2020-08-05 6:37 UTC: https://lore.kernel.org/git/?q=%22negative+refspecs%22 So maybe it was a delay due to Xapian's MVCC mechanism; but that shouldn't be HOURS off (maybe minutes at most), assuming you tried to search shortly before you sent the message I'm replying to at 22:12 UTC... My v1 instance at public-inbox.org (which uses Xapian 1.4 and the "glass" backend) shows it, too: https://public-inbox.org/git/?q=%22negative+refspecs%22 You could also try NEAR and ADJ (I don't have much experience with those): https://xapian.org/docs/queryparser.html
next prev parent reply other threads:[~2020-08-07 8:04 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 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 [this message] 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=20200807080436.GA21342@dcvr \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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).