public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/ddcutil/
Date: Fri, 15 Apr 2022 05:30:19 +0000 (UTC)	[thread overview]
Message-ID: <1650000610.7b9d38158e270d39c7ece9479b894b9c8a361753.sam@gentoo> (raw)

commit:     7b9d38158e270d39c7ece9479b894b9c8a361753
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 15 05:30:10 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 15 05:30:10 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7b9d3815

app-misc/ddcutil: add note to bump/cleanup w app-misc/ddcui

Bug: https://bugs.gentoo.org/787020
Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-misc/ddcutil/ddcutil-1.2.2.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/app-misc/ddcutil/ddcutil-1.2.2.ebuild b/app-misc/ddcutil/ddcutil-1.2.2.ebuild
index 91a57f143aeb..9aa77c1cc2d3 100644
--- a/app-misc/ddcutil/ddcutil-1.2.2.ebuild
+++ b/app-misc/ddcutil/ddcutil-1.2.2.ebuild
@@ -3,6 +3,8 @@
 
 EAPI=8
 
+# Check for bumps & cleanup with app-misc/ddcui
+
 inherit autotools linux-info udev
 
 DESCRIPTION="Program for querying and changing monitor settings"


             reply	other threads:[~2022-04-15  5:30 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  5:30 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27 16:04 [gentoo-commits] repo/gentoo:master commit in: app-misc/ddcutil/ Sam James
2025-02-27  6:05 Sam James
2025-02-26  4:50 Sam James
2025-01-08  9:37 Nowa Ammerlaan
2024-10-30 19:59 Sam James
2024-10-27  6:50 Arthur Zamarin
2024-10-25 21:25 Sam James
2024-10-25 21:25 Sam James
2024-10-25 21:25 Sam James
2024-02-24 11:32 Andrew Ammerlaan
2024-02-24 11:32 Andrew Ammerlaan
2024-02-17 21:17 Sam James
2024-02-08  9:06 Andrew Ammerlaan
2024-02-08  9:06 Andrew Ammerlaan
2024-02-01  9:41 Andrew Ammerlaan
2024-02-01  9:41 Andrew Ammerlaan
2024-01-22 13:43 Andrew Ammerlaan
2023-12-11  7:31 Andrew Ammerlaan
2023-12-01 18:58 Arthur Zamarin
2023-11-24  9:37 Andrew Ammerlaan
2023-11-24  9:37 Andrew Ammerlaan
2023-06-30 21:14 Sam James
2023-06-30 21:14 Sam James
2023-06-30 21:14 Sam James
2023-06-30 19:30 Sam James
2023-06-30 19:19 Sam James
2022-08-28  5:06 WANG Xuerui
2022-04-15  5:00 Robin H. Johnson
2022-02-21 19:47 Andrew Ammerlaan
2022-02-21 19:47 Andrew Ammerlaan
2022-01-10 11:47 Andrew Ammerlaan
2022-01-10 11:47 Andrew Ammerlaan
2021-08-18  0:35 Yixun Lan
2021-07-09 22:48 Conrad Kostecki
2021-07-09 22:48 Conrad Kostecki
2021-07-09 22:36 Conrad Kostecki
2021-07-09 22:36 Conrad Kostecki
2020-07-30 23:07 Robin H. Johnson
2020-05-18 22:39 Georgy Yakovlev
2019-07-15 23:16 Manuel Rüger
2019-07-15 23:16 Manuel Rüger
2019-02-26 20:54 Andreas Sturmlechner
2018-08-04 17:48 Jonathan Scruggs
2018-08-04 16:31 Jonathan Scruggs
2018-01-27 17:19 Jonathan Scruggs
2018-01-26 13:03 Jeroen Roovers
2018-01-25 21:35 Jonathan Scruggs
2017-10-10 13:50 Michael Palimaka
2017-09-23  8:38 David Seifert
2017-08-16 21:00 Michał Górny
2017-08-16 21:00 Michał Górny
2017-01-29 17:09 Michael Palimaka
2017-01-29 17:09 Michael Palimaka
2017-01-15 11:14 David Seifert

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=1650000610.7b9d38158e270d39c7ece9479b894b9c8a361753.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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