All of lore.kernel.org
 help / color / mirror / Atom feed
From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/python-entrypoints: new package
Date: Mon, 21 Oct 2019 22:31:57 +0300	[thread overview]
Message-ID: <CALFsTFXKiXB0FFRH0xyY1VGuFbHXV+nTBsWVHdiUQNoKuUCr8A@mail.gmail.com> (raw)
In-Reply-To: <20191021211959.2937fa72@windsurf>

Hello,

On Mon, Oct 21, 2019 at 10:20 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello Asaf,
>
> On Mon, 21 Oct 2019 22:01:27 +0300
> Asaf Kahlon <asafka7@gmail.com> wrote:
>
> > Yes, python-entrypoints was sent together with python-keyring.
>
> Together, but mixed with the other patches I supposed ?
>

Yes.

> > In addition, python-zc-lockfile was sent together with python-cherrypy.
> > Moreover, I now noticed that my series of python-snmp-apps with
> > snmpclitools earlier
> > this month seems to be sent separately too. All the other patches I
> > sent are single patches.
> > Next time, I'll send the series at the same time.
> > Do you need me to resend the existing patches or we'll be fine for that round?
>
> No need to resend.

OK, thanks :)

>
> > > 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 ?
> > >
> >
> > Indeed, I updated the packages mostly because of the new e-mail feature with the
> > list of outdated packages.
> > I guess those many bumps happened since the feature is new and we had
> > a lot to do, but I think now we're pretty close to the end, so the
> > stream of patches is going to reduce :)
>
> Great :-) In any case, thanks for doing this work!
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

Asaf.

  reply	other threads:[~2019-10-21 19:31 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
2019-10-21 19:01     ` Asaf Kahlon
2019-10-21 19:19       ` Thomas Petazzoni
2019-10-21 19:31         ` Asaf Kahlon [this message]
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=CALFsTFXKiXB0FFRH0xyY1VGuFbHXV+nTBsWVHdiUQNoKuUCr8A@mail.gmail.com \
    --to=asafka7@gmail.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.