From: tavianator <tavianator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] bfs: update to 2.6.2.
Date: Sat, 22 Oct 2022 18:22:56 +0200 [thread overview]
Message-ID: <20221022162256.m7ovCCJhus7Cby34_DjlKwyKFPoRpsBZMJJkfjqas24@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40090@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 205 bytes --]
New comment by tavianator on void-packages repository
https://github.com/void-linux/void-packages/pull/40090#issuecomment-1287842827
Comment:
You can also work around it with `export BFS_TRIED_DROP=""`
next prev parent reply other threads:[~2022-10-22 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 21:52 [PR PATCH] " daniel-eys
2022-10-21 21:58 ` daniel-eys
2022-10-22 0:42 ` [WIP] " tavianator
2022-10-22 16:22 ` tavianator [this message]
2022-10-23 13:34 ` [PR PATCH] [Updated] " daniel-eys
2022-10-23 13:38 ` daniel-eys
2023-01-22 2:00 ` github-actions
2023-01-22 12:11 ` [PR PATCH] [Merged]: " leahneukirchen
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=20221022162256.m7ovCCJhus7Cby34_DjlKwyKFPoRpsBZMJJkfjqas24@z \
--to=tavianator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).