From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libnss: bump version to 3.67
Date: Tue, 20 Jul 2021 23:33:34 +0200 [thread overview]
Message-ID: <20210720233334.2143daf9@windsurf> (raw)
In-Reply-To: <900065c9-8832-df20-35ac-ea69cbfe72e4@benettiengineering.com>
On Tue, 20 Jul 2021 23:09:05 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Sure I can. Here there is a "problem" if we can call it that way. It's
> from some month that they release very very fast. Now they are at NSS
> 3.68 and NSPR 4.32 [1], but very soon there will be version 3.69. Even
> if I send version bumps, they will release another version before you
> apply for sure. Let's see if it gets slower.
> They also stopped emitting the Release Notes that doesn't help[2].
>
> What can I do? Do I send the latest I see in the moment I bump and
> that's it, right?
Correct. Whenever you see a new version, send a new patch series which
is based on the latest master, and mark your previous patches in
patchwork as "Superseded".
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Joseph Kogut <joseph.kogut@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libnss: bump version to 3.67
Date: Tue, 20 Jul 2021 23:33:34 +0200 [thread overview]
Message-ID: <20210720233334.2143daf9@windsurf> (raw)
Message-ID: <20210720213334.VA9kjOCm4yrj2ZAAC5s5EKi6ZjrkhFG3LCSEIjxvlJQ@z> (raw)
In-Reply-To: <900065c9-8832-df20-35ac-ea69cbfe72e4@benettiengineering.com>
On Tue, 20 Jul 2021 23:09:05 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Sure I can. Here there is a "problem" if we can call it that way. It's
> from some month that they release very very fast. Now they are at NSS
> 3.68 and NSPR 4.32 [1], but very soon there will be version 3.69. Even
> if I send version bumps, they will release another version before you
> apply for sure. Let's see if it gets slower.
> They also stopped emitting the Release Notes that doesn't help[2].
>
> What can I do? Do I send the latest I see in the moment I bump and
> that's it, right?
Correct. Whenever you see a new version, send a new patch series which
is based on the latest master, and mark your previous patches in
patchwork as "Superseded".
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-20 21:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 17:35 [Buildroot] [PATCH] package/libnss: bump version to 3.67 Giulio Benetti
2021-06-12 17:38 ` Giulio Benetti
2021-07-20 20:44 ` Thomas Petazzoni
2021-07-20 20:44 ` Thomas Petazzoni
2021-07-20 21:09 ` Giulio Benetti
2021-07-20 21:09 ` Giulio Benetti
2021-07-20 21:33 ` Thomas Petazzoni [this message]
2021-07-20 21:33 ` Thomas Petazzoni
2021-07-22 23:35 ` [Buildroot] [PATCH 0/2] Bump NSS and NSPR Giulio Benetti
2021-07-22 23:35 ` [Buildroot] [PATCH 1/2] package/libnspr: bump to version 4.32 Giulio Benetti
2021-07-22 23:35 ` [Buildroot] [PATCH 2/2] package/libnss: bump to version 3.68 Giulio Benetti
2021-07-25 13:09 ` [Buildroot] [PATCH 0/2] Bump NSS and NSPR 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=20210720233334.2143daf9@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.