From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Leonid Yuriev <leo@yuriev.ru>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-30
Date: Thu, 01 Dec 2022 21:59:01 +0100 [thread overview]
Message-ID: <87edtic02y.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221201174145.5e70863c@windsurf> (Thomas Petazzoni via buildroot's message of "Thu, 1 Dec 2022 17:41:45 +0100")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> On Thu, 1 Dec 2022 19:01:55 +0300
> Leonid Yuriev <leo@yuriev.ru> wrote:
>> Commit f54bf3ecc638b62162a43f8c276407ad1ffa0dd4
> Thanks, but please keep the Buildroot mailing list in Cc when replying
> :-)
Are you sure about that commit? We don't seem to such a commit in
buildroot, and as far as I can see on
https://gitflic.ru/project/erthink/libmdbx/commit/f54bf3ecc638b62162a43f8c276407ad1ffa0dd4,
neither does upstream libmdbx?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-01 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221201104313.25K7I8a6@myt5-1a3effcffc39.qloud-c.yandex.net>
[not found] ` <3b7ef091-b01c-59d3-d31b-8b28e59bf1df@yuriev.ru>
2022-12-01 15:51 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-11-30 Thomas Petazzoni via buildroot
[not found] ` <a89a5a97-317a-b634-65ad-5fa11e526bc0@yuriev.ru>
2022-12-01 16:41 ` Thomas Petazzoni via buildroot
2022-12-01 20:59 ` Peter Korsgaard [this message]
2022-12-01 21:08 ` Leonid Yuriev
2022-12-01 21:22 ` Peter Korsgaard
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=87edtic02y.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=leo@yuriev.ru \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.