From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 3.5.18
Date: Sat, 07 May 2016 14:47:44 +0200 [thread overview]
Message-ID: <28d33bd9-b676-9374-4ae5-872902f3844b@ipfire.org> (raw)
In-Reply-To: <1462624422.18591.122.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
Hi,
On 07.05.2016 14:33, Michael Tremer wrote:
>> > Could you please link to the orignal resource and not to a mirror next time?
>> > The
>> > mirror might go down and URLs won't work any more then.
I'd love to, but I couldn't find an appropriate statement for the
current version, not even in:
https://github.com/squid-cache/squid/blob/master/ChangeLog (looong list).
Searching again, the nearest hit was:
ftp://ftp.fu-berlin.de/unix/www/squid/archive/3.1/squid-3.1.5-RELEASENOTES.html
("Changes to existing options").
> Just realised that this one is pointing to a completely different release any
> way
;-)
The trick is, 'squid' doesn't even throw an error if you use these (or
other) "deprecated" options. Great...
Best,
Matthias
prev parent reply other threads:[~2016-05-07 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 11:01 Matthias Fischer
2016-05-07 12:32 ` Michael Tremer
2016-05-07 12:33 ` Michael Tremer
2016-05-07 12:47 ` Matthias Fischer [this message]
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=28d33bd9-b676-9374-4ae5-872902f3844b@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@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