From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/dtv-scan-tables: bump version
Date: Sun, 10 Jun 2018 14:12:20 +0200 [thread overview]
Message-ID: <20180610141220.336c8703@windsurf> (raw)
In-Reply-To: <20180610101415.20349-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 10 Jun 2018 12:14:15 +0200, Bernd Kuhls wrote:
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/dtv-scan-tables/dtv-scan-tables.hash | 2 +-
> package/dtv-scan-tables/dtv-scan-tables.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks. However, for bumps from a random Git commit
to another random Git commit, it would be good to indicate what was the
motivation for the bump. Indeed, if we start bumping every day packages
that are fetched from Git based on a commit ID, we will have gazillions
of bump patches :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-10 12:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 10:14 [Buildroot] [PATCH 1/1] package/dtv-scan-tables: bump version Bernd Kuhls
2018-06-10 12:12 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-14 13:41 Bernd Kuhls
2025-06-15 10:58 ` Julien Olivain
2024-07-26 16:45 Bernd Kuhls
2024-08-02 19:24 ` Thomas Petazzoni via buildroot
2022-07-03 13:01 Bernd Kuhls
2022-07-08 7:35 ` Peter Korsgaard
2021-12-12 9:05 Bernd Kuhls
2021-12-12 15:13 ` Arnout Vandecappelle
2021-12-12 16:01 ` Yann E. MORIN
2019-06-24 19:22 Bernd Kuhls
2019-06-25 18:58 ` Peter Korsgaard
2018-04-10 19:09 Bernd Kuhls
2018-04-11 14:18 ` Thomas Petazzoni
2016-06-01 19:15 Bernd Kuhls
2016-06-01 19:21 ` Peter Korsgaard
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=20180610141220.336c8703@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox