From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libmicrohttpd 0.9.71: Fix for rootfile
Date: Fri, 03 Jul 2020 12:43:50 +0200 [thread overview]
Message-ID: <381b3265-36c4-7272-e807-6dd8a6e2ab31@ipfire.org> (raw)
In-Reply-To: <1F702DA3-8074-46F0-B9B4-FCC9D1F4CA6C@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 253 bytes --]
On 03.07.2020 11:37, Michael Tremer wrote:
> Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
>
> Meh. That is 10 pence into the kitty. :)
> ...
Yep. I raise a quarter...
I must have just been looking in the other direction.
Best,
Matthias
next prev parent reply other threads:[~2020-07-03 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 20:51 Matthias Fischer
2020-07-03 9:37 ` Michael Tremer
2020-07-03 10:43 ` Matthias Fischer [this message]
2020-07-03 21: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=381b3265-36c4-7272-e807-6dd8a6e2ab31@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