From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: squid update to 3.4.14
Date: Fri, 07 Aug 2015 14:26:55 +0100 [thread overview]
Message-ID: <1438954015.3686.24.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
Hello Matthias,
I just saw that you already uploaded the squid tarball to the source
server a few days ago. Hence I assume you have a patch for the update
somewhere.
I was about to update the package, but if you did that already, I would
rather like to just pull the patch. Could not find anything in your
repository.
Could you please send the patch if it is ready? Are you otherwise still
debugging some issues with the version update?
Best,
-Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2015-08-07 13:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1438954015.3686.24.camel@ipfire.org \
--to=michael.tremer@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