From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] package/poco: bump to version 1.10.1
Date: Mon, 29 Jun 2020 23:18:28 +0200 [thread overview]
Message-ID: <20200629231828.2222716b@windsurf> (raw)
In-Reply-To: <20200629210735.179913-2-juju@cotds.org>
On Mon, 29 Jun 2020 23:07:33 +0200
Julien Olivain <juju@cotds.org> wrote:
> +Subject: [PATCH 1/3] poco: add the staging path to search path
Please generate patches with "git format-patch -N" to not have the 1/3,
2/3, 3/3 part. "make check-package" normally warns about this.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-29 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 21:07 [Buildroot] [PATCH 1/4] package/poco: fix the comment dependencies about riscv Julien Olivain
2020-06-29 21:07 ` [Buildroot] [PATCH 2/4] package/poco: bump to version 1.10.1 Julien Olivain
2020-06-29 21:18 ` Thomas Petazzoni [this message]
2020-06-29 21:07 ` [Buildroot] [PATCH 3/4] package/poco: enable build for riscv64 Julien Olivain
2020-06-29 21:19 ` Thomas Petazzoni
2020-06-29 21:07 ` [Buildroot] [PATCH 4/4] package/poco: add new option for the Poco JWT component Julien Olivain
2020-06-29 21:21 ` Thomas Petazzoni
2020-06-29 21:17 ` [Buildroot] [PATCH 1/4] package/poco: fix the comment dependencies about riscv Thomas Petazzoni
2020-06-30 17:34 ` [Buildroot] [PATCH v2 1/4] package/poco: add BR2_PACKAGE_POCO_ARCH_SUPPORTS Julien Olivain
2020-06-30 17:34 ` [Buildroot] [PATCH v2 2/4] package/poco: bump to version 1.10.1 Julien Olivain
2020-06-30 17:34 ` [Buildroot] [PATCH v2 3/4] package/poco: enable build for riscv64 Julien Olivain
2020-06-30 17:34 ` [Buildroot] [PATCH v2 4/4] package/poco: add new option for the Poco JWT component Julien Olivain
2020-06-30 20:15 ` [Buildroot] [PATCH v2 1/4] package/poco: add BR2_PACKAGE_POCO_ARCH_SUPPORTS Yann E. MORIN
2020-07-16 16:40 ` 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=20200629231828.2222716b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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.