From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v1] package/ripgrep: bump version to 12.1.1
Date: Sat, 5 Dec 2020 21:25:30 +0100 [thread overview]
Message-ID: <20201205212530.68a9bab3@windsurf.home> (raw)
In-Reply-To: <20201202201551.6380-1-ps.report@gmx.net>
On Wed, 2 Dec 2020 21:15:51 +0100
Peter Seiderer <ps.report@gmx.net> wrote:
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/ripgrep/ripgrep.hash | 4 ++--
> package/ripgrep/ripgrep.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
This bump is already part of my series adding a Cargo package
infrastructure *and* adding support for Cargo vendoring. And having the
bump as part of this series is important, as the contents of the
tarball changes, and therefore its hashes changes, which requires doing
the bump together with the introduction of Cargo vendoring.
So I'd like to keep the bump part of this series, if you don't mind.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-12-05 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 20:15 [Buildroot] [PATCH/next v1] package/ripgrep: bump version to 12.1.1 Peter Seiderer
2020-12-05 20:25 ` Thomas Petazzoni [this message]
2020-12-07 18:44 ` Peter Seiderer
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=20201205212530.68a9bab3@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