All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/python-entrypoints: new package
Date: Mon, 21 Oct 2019 19:13:28 +0200	[thread overview]
Message-ID: <20191021191328.201217a0@windsurf> (raw)
In-Reply-To: <20191021134031.20586-4-asafka7@gmail.com>

Hello Asaf,

On Mon, 21 Oct 2019 16:40:24 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:

> Signed-off-by: Asaf Kahlon <asafka7@gmail.com>

Could you send the patches that go together, at the same time ? Here I
had a long list of patches PATCH 1/1, and in the middle of them, this
PATCH 1/2, which I guess goes with "package/python-keyring: bump to
version  19.2.0". Having them sent separately is quite confusing.

Could you make sure to send series as proper series, this would really
makes things a bit easier.

Also, I see you are doing a lot of version bumps for Python packages.
Is it related to the fact that you know receive e-mail notifications
when Python packages are not up to date ? Are we going to see a point
where this stream of patches reduces, or is there just very frequent
update of Python modules happening upstream ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-21 17:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 13:40 [Buildroot] [PATCH 1/1] package/python-asn1crypyo: bump to version 1.2.0 Asaf Kahlon
2019-10-21 13:40 ` [Buildroot] [PATCH 1/1] package/python-cheroot: bump to version 8.2.1 Asaf Kahlon
2019-10-21 17:11   ` Thomas Petazzoni
2019-10-21 13:40 ` [Buildroot] [PATCH 1/1] package/python-docker: bump to version 4.1.0 Asaf Kahlon
2019-10-21 17:11   ` Thomas Petazzoni
2019-10-23 15:40   ` Peter Korsgaard
2019-10-23 19:20     ` Asaf Kahlon
2019-10-23 19:46       ` Peter Korsgaard
2019-10-21 13:40 ` [Buildroot] [PATCH 1/2] package/python-entrypoints: new package Asaf Kahlon
2019-10-21 17:13   ` Thomas Petazzoni [this message]
2019-10-21 19:01     ` Asaf Kahlon
2019-10-21 19:19       ` Thomas Petazzoni
2019-10-21 19:31         ` Asaf Kahlon
2019-10-21 21:17           ` Thomas Petazzoni
2020-02-02 19:49   ` Peter Korsgaard
2019-10-21 13:40 ` [Buildroot] [PATCH 1/1] package/python-flask-sqlalchemy: bump to version 2.4.1 Asaf Kahlon
2019-10-21 17:13   ` Thomas Petazzoni
2019-10-21 13:40 ` [Buildroot] [PATCH 1/1] package/python-flup: bump to version 1.0.3 Asaf Kahlon
2019-10-21 17:13   ` Thomas Petazzoni
2019-10-21 13:40 ` [Buildroot] [PATCH 1/1] package/python-pymodbus: bump to version 2.2.0 Asaf Kahlon
2019-10-21 17:13   ` Thomas Petazzoni
2019-10-21 13:40 ` [Buildroot] [PATCH 1/1] package/python-xlsxwriter: bump to version 1.2.2 Asaf Kahlon
2019-10-21 17:13   ` Thomas Petazzoni
2019-10-21 13:40 ` [Buildroot] [PATCH 1/2] package/python-zc-lockfile: new package Asaf Kahlon
2020-02-04  9:58   ` Peter Korsgaard
2019-10-21 13:40 ` [Buildroot] [PATCH 2/2] package/python-cherrypy: bump to version 18.3.0 Asaf Kahlon
2020-02-04 10:03   ` Peter Korsgaard
2019-10-21 13:40 ` [Buildroot] [PATCH 2/2] package/python-keyring: bump to version 19.2.0 Asaf Kahlon
2020-04-13 19:54   ` Thomas Petazzoni
2019-10-21 17:11 ` [Buildroot] [PATCH 1/1] package/python-asn1crypyo: bump to version 1.2.0 Thomas Petazzoni

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=20191021191328.201217a0@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.