From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 4.4 (stable)
Date: Wed, 19 Dec 2018 18:54:43 +0100 [thread overview]
Message-ID: <96922ea3-6d4a-f9ad-7685-e6483bd884b1@ipfire.org> (raw)
In-Reply-To: <36903BA6-7CA8-46E0-9670-304583696FA1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]
On 19.12.2018 18:46, Michael Tremer wrote:
> Hi,
>
>> On 19 Dec 2018, at 17:45, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> On 19.12.2018 17:10, Michael Tremer wrote:
>>> Sorry from me as well for overlooking that.
>>
>> No problem... ;-)
>>
>>> Merged and the nightly build ran through…
>>
>> Ok, thanks for the feedback - in between I thought there were still
>> mistakes in it. That d*** "binary blob" came from my installation
>> archive - I forgot to delete it *twice* before pushing! Duh! Now I'm
>> using a dedicated 'upload'-directory for these archives, so this won't
>> happen again…
>>
> No worries. Shit happens.
>
>> On my production machine this build is running without any errors since
>> then.
>
> Good. I will install this as soon as possible. I still don’t quite believe that nothing in the configuration has to be changed.
'squid - k parse' never showed any errors and the GUI didn't make any
problems until now. We'll see.
> We still have Daniel’s patch that hasn’t been integrated. Do you have time to look into that again, too? I forget where that got stuck…
I can do that - its running here - work in progress. ;-)
Best,
Matthias
> -Michael
>
>>
>> Best,
>> Matthias
>>
>>
>>> -Michael
>>>
>>>> On 17 Dec 2018, at 18:52, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>
>>>> On 17.12.2018 18:19, Michael Tremer wrote:
>>>>> Hey,
>>>>
>>>> Hi,
>>>>
>>>>> this patch has a binary blob in it. That is why it is so large.
>>>>
>>>> Yep. Sorry for the noise, but it seems I "stood a bit beside me" while
>>>> sending this.
>>>>
>>>>> I guess you want to resend that?!
>>>>
>>>> Exactly. I did that already - please take a look at:
>>>>
>>>> =>
>>>> https://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=commit;h=c9164e6a7fde32f25ded6e2441ce87919b1af5c9
>>>>
>>>> And:
>>>>
>>>> => https://patchwork.ipfire.org/patch/1998/
>>>>
>>>> Best,
>>>> Matthias
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
next parent reply other threads:[~2018-12-19 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36903BA6-7CA8-46E0-9670-304583696FA1@ipfire.org>
2018-12-19 17:54 ` Matthias Fischer [this message]
2018-12-20 20:05 ` Matthias Fischer
2018-12-21 14:28 ` Michael Tremer
[not found] <20181213173224.11553-1-matthias.fischer@ipfire.org>
2018-12-17 17:19 ` Michael Tremer
2018-12-17 18:52 ` Matthias Fischer
2018-12-19 16:10 ` Michael Tremer
2018-12-13 17:40 Matthias Fischer
-- strict thread matches above, loose matches on Subject: below --
2018-11-04 7:09 Matthias Fischer
2018-11-09 15:22 ` Michael Tremer
2018-11-09 18:56 ` Matthias Fischer
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=96922ea3-6d4a-f9ad-7685-e6483bd884b1@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