From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/luaossl: bump to version 20190731
Date: Tue, 20 Aug 2019 14:26:14 +0200 [thread overview]
Message-ID: <20190820142614.7dad1d74@windsurf.home> (raw)
In-Reply-To: <20190820082542.14610-1-m.niestroj@grinn-global.com>
Hello Marcin,
On Tue, 20 Aug 2019 10:25:42 +0200
Marcin Niestroj <m.niestroj@grinn-global.com> wrote:
> Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
> ---
> package/luaossl/luaossl.hash | 4 ++--
> package/luaossl/luaossl.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
We're already at version 20190731 in the next branch. When sending
version bumps, if we're after -rc1, make sure to check the "next"
branch, as this is where we merge version bumps and other changes that
are not important/critical for the upcoming release.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-20 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 8:25 [Buildroot] [PATCH] package/luaossl: bump to version 20190731 Marcin Niestroj
2019-08-20 12:26 ` Thomas Petazzoni [this message]
2019-08-20 12:59 ` Marcin Niestrój
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=20190820142614.7dad1d74@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