From: Peter Korsgaard <peter@korsgaard.com>
To: Peter Seiderer <ps.report@gmx.net>
Cc: "Maxim Kochetkov" <fido_max@inbox.ru>,
"Vincent Stehlé" <vincent.stehle@laposte.net>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 4/5] package/osm2pgsql: fix double space in Config.in comment
Date: Mon, 10 Apr 2023 21:21:15 +0200 [thread overview]
Message-ID: <87sfd7v904.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230326080034.14629-4-ps.report@gmx.net> (Peter Seiderer's message of "Sun, 26 Mar 2023 10:00:33 +0200")
>>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Committed to 2023.02.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-04-10 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 8:00 [Buildroot] [PATCH v1 1/5] package/protozero: fix double space in Config.in comment Peter Seiderer
2023-03-26 8:00 ` [Buildroot] [PATCH v1 2/5] package/lcdproc: " Peter Seiderer
2023-04-10 19:20 ` Peter Korsgaard
2023-03-26 8:00 ` [Buildroot] [PATCH v1 3/5] package/libosmium: " Peter Seiderer
2023-03-26 18:31 ` Maxim Kochetkov via buildroot
2023-04-10 19:20 ` Peter Korsgaard
2023-03-26 8:00 ` [Buildroot] [PATCH v1 4/5] package/osm2pgsql: " Peter Seiderer
2023-03-26 18:32 ` Maxim Kochetkov via buildroot
2023-04-10 19:21 ` Peter Korsgaard [this message]
2023-03-26 8:00 ` [Buildroot] [PATCH v1 5/5] package/zerofree: " Peter Seiderer
2023-04-10 19:21 ` Peter Korsgaard
2023-03-26 18:31 ` [Buildroot] [PATCH v1 1/5] package/protozero: " Maxim Kochetkov via buildroot
2023-03-26 20:01 ` Thomas Petazzoni via buildroot
2023-04-10 19:18 ` 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=87sfd7v904.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fido_max@inbox.ru \
--cc=ps.report@gmx.net \
--cc=vincent.stehle@laposte.net \
/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.