From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] package/python-certifi: bump version to 2019.6.16
Date: Sun, 4 Aug 2019 12:11:04 +0200 [thread overview]
Message-ID: <20190804121104.36dc5856@windsurf.home> (raw)
In-Reply-To: <8736ih8eam.fsf@tarshish>
On Sun, 04 Aug 2019 12:34:25 +0300
Baruch Siach <baruch@tkos.co.il> wrote:
> > Series applied. Thanks!
>
> Patch http://patchwork.ozlabs.org/patch/1141604/
> (package/python-urllib3: bump version to 1.25.3) is not in master as of
> commit e98fc11afb.
Sorry about that, I indeed messed things up, trying to do to many
things at once. I now applied the patch for real and pushed it. Thanks
for noticing!
BTW, Baruch, we're wondering how you notice this kind of things ? Do
you have some tool that checks this, or your brain is just so good that
it can detect this kind of mistakes ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-04 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 20:40 [Buildroot] [PATCH 1/5] package/python-certifi: bump version to 2019.6.16 Bernd Kuhls
2019-08-03 20:40 ` [Buildroot] [PATCH 2/5] package/python-oauthlib: bump version to 3.0.2 Bernd Kuhls
2019-08-03 20:40 ` [Buildroot] [PATCH 3/5] package/python-requests-oauthlib: bump version to 1.2.0 Bernd Kuhls
2019-08-03 20:40 ` [Buildroot] [PATCH 4/5] package/python-urllib3: bump version to 1.25.3 Bernd Kuhls
2019-08-03 20:40 ` [Buildroot] [PATCH 5/5] package/python-mwclient: bump version to 0.10.0 Bernd Kuhls
2019-08-04 9:24 ` [Buildroot] [PATCH 1/5] package/python-certifi: bump version to 2019.6.16 Thomas Petazzoni
2019-08-04 9:34 ` Baruch Siach
2019-08-04 10:11 ` Thomas Petazzoni [this message]
2019-08-04 10:44 ` Baruch Siach
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=20190804121104.36dc5856@windsurf.home \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox