public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/merge-usr/
Date: Sat,  3 Dec 2022 18:32:59 +0000 (UTC)	[thread overview]
Message-ID: <1670092374.09bec241a7c605c7500a1e5201462d2a129bbf7d.floppym@gentoo> (raw)

commit:     09bec241a7c605c7500a1e5201462d2a129bbf7d
Author:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Sat Dec  3 18:32:06 2022 +0000
Commit:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Sat Dec  3 18:32:54 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=09bec241

sys-apps/merge-usr: add 6, drop 5

Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>

 sys-apps/merge-usr/Manifest                                   | 2 +-
 sys-apps/merge-usr/{merge-usr-5.ebuild => merge-usr-6.ebuild} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/merge-usr/Manifest b/sys-apps/merge-usr/Manifest
index af540161fb82..74189a4f7b19 100644
--- a/sys-apps/merge-usr/Manifest
+++ b/sys-apps/merge-usr/Manifest
@@ -1 +1 @@
-DIST merge-usr-5.tar.gz 9492 BLAKE2B 5fbd23a59f76004a1548ae230a4eccc9ecc81a36b235ed8744fd48cd980815c62929fb436068dd232812d92c39ed5f7d778ffe2ddbaaf4f9c7785c6927d6eb87 SHA512 b0b4d8da51a570057ce9aeccd4cf880c2a6bc52067958e23e5162d589b671a123ddbdab8a74dd5f076f689be737637e1b1a7b0581e94bfbae4e16ada37be6045
+DIST merge-usr-6.tar.gz 9501 BLAKE2B 3cdb769c1f75cb35a941c6ba6fe1d469e38bb0e96ce7aeac6fa6b8cfead4b630a13eac7b03144bb00f35a722a5264b39a504826e442d3c44b12d505c911d14a2 SHA512 57cbf2fadac587747b10f88299224e2c40a7a9375c0fc502ad966f42cf87f034b0b28d195001b275869f90dd1eecf210c47ffce9cd0163cc01b67b7860a680e4

diff --git a/sys-apps/merge-usr/merge-usr-5.ebuild b/sys-apps/merge-usr/merge-usr-6.ebuild
similarity index 100%
rename from sys-apps/merge-usr/merge-usr-5.ebuild
rename to sys-apps/merge-usr/merge-usr-6.ebuild


             reply	other threads:[~2022-12-03 18:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03 18:32 Mike Gilbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-13 15:26 [gentoo-commits] repo/gentoo:master commit in: sys-apps/merge-usr/ Mike Gilbert
2022-12-01 18:04 Sam James
2022-12-01 18:03 Sam James
2022-12-01 18:03 Sam James
2022-12-01 18:03 Sam James
2022-12-01 18:03 Sam James
2022-12-01 18:03 Sam James
2022-12-01 18:03 Sam James
2022-12-01 18:03 Sam James
2022-12-01 16:45 Mike Gilbert
2022-11-04 16:17 Mike Gilbert
2022-11-02 20:11 Mike Gilbert
2022-10-30 20:18 Mike Gilbert
2022-10-21 21:24 Mike Gilbert
2022-10-21 21:24 Mike Gilbert
2022-10-07  8:47 WANG Xuerui
2022-09-26  7:31 Michał Górny
2022-09-14  2:39 Yixun Lan
2022-09-10 23:06 Mike Gilbert
2022-09-10 15:29 James Le Cuirot
2022-09-04 18:25 Arthur Zamarin
2022-09-04 18:25 Arthur Zamarin
2022-09-04 18:21 Arthur Zamarin
2022-09-04  0:29 Sam James
2022-09-03 21:32 Jakov Smolić
2022-09-03 21:32 Jakov Smolić
2022-09-03 21:30 Jakov Smolić
2022-09-03 21:30 Jakov Smolić
2022-09-03 18:12 Arthur Zamarin
2022-09-03 18:12 Arthur Zamarin
2022-09-03 16:49 Arthur Zamarin
2022-09-03 16:49 Arthur Zamarin
2022-08-30 19:38 Sam James
2022-08-30 17:58 Mike Gilbert

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=1670092374.09bec241a7c605c7500a1e5201462d2a129bbf7d.floppym@gentoo \
    --to=floppym@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