From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Question regarding commit 3bc852b993a0d4c4f519c4d96eb246170f953d50
Date: Tue, 05 May 2020 21:08:38 +0100 [thread overview]
Message-ID: <F34C3335-22AE-4D91-957F-F2579621242A@ipfire.org> (raw)
In-Reply-To: <087ef428-d95f-dd58-8663-9f66016d66a4@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Hi,
Yes, I dropped those because the syntax was invalid.
We do not have a parser for those and so they could not be used.
-Michael
> On 5 May 2020, at 20:56, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hi Michael,
>
> in 3bc852b993a0d4c4f519c4d96eb246170f953d50 you removed all the Autonomous
> Systems from the override files. These were pretty handy for ASNs of VPN
> or Tor (exit) relay providers, which is why I vote for re-adding them.
>
> What is your opinion on this?
>
> Thanks, and best regards,
> Peter Müller
next prev parent reply other threads:[~2020-05-05 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 19:56 Peter Müller
2020-05-05 20:08 ` Michael Tremer [this message]
2020-05-05 20:12 ` Peter Müller
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=F34C3335-22AE-4D91-957F-F2579621242A@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@lists.ipfire.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