public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/uglifyjs/
Date: Sun, 15 May 2022 08:30:03 +0000 (UTC)	[thread overview]
Message-ID: <1652603389.01949003a47c8b08f24f9037cf3ab587c529ec71.chewi@gentoo> (raw)

commit:     01949003a47c8b08f24f9037cf3ab587c529ec71
Author:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Sun May 15 08:29:49 2022 +0000
Commit:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Sun May 15 08:29:49 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01949003

dev-util/uglifyjs: Bump to 3.15.5, drop old 3.15.4

Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>

 dev-util/uglifyjs/Manifest                                           | 2 +-
 dev-util/uglifyjs/{uglifyjs-3.15.4.ebuild => uglifyjs-3.15.5.ebuild} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/uglifyjs/Manifest b/dev-util/uglifyjs/Manifest
index 2fd75be42f67..b74a84638c45 100644
--- a/dev-util/uglifyjs/Manifest
+++ b/dev-util/uglifyjs/Manifest
@@ -1 +1 @@
-DIST uglifyjs-3.15.4.tar.gz 512680 BLAKE2B 428d18b412a7b30fb9fd0491e0bca1f8ad0d176726885bba9afe155622860abfd2d723d11c03b2381cb500074f3c1041f7ae4d35c3f1f3b8e3713c39ee3d5069 SHA512 203d06eeda62ce0810c0188640b88ae08e567610bb0573f962341c4cd4b39ca63ce0d0fcd1e4749384afbc6f64079db6bc101eab31af95caefc1088c2e0dca59
+DIST uglifyjs-3.15.5.tar.gz 513343 BLAKE2B 7968da6bb644210a69c5ea3125ab7e6a5879d23204b0f045a607a7b207a017bb880705fe654ab346a87c0559c8dd892a16a818c5163e91d8e0963a2daec5d8ad SHA512 9018c537d09c5e95f8366ba9c5eeabdfd3763cd1c87a7a0af0ebd02090f53829b99f4f672dab2580fa801a6af799ca0e99f1e6f32d79f079ff0d5d11f4309ecd

diff --git a/dev-util/uglifyjs/uglifyjs-3.15.4.ebuild b/dev-util/uglifyjs/uglifyjs-3.15.5.ebuild
similarity index 100%
rename from dev-util/uglifyjs/uglifyjs-3.15.4.ebuild
rename to dev-util/uglifyjs/uglifyjs-3.15.5.ebuild


             reply	other threads:[~2022-05-15  8:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15  8:30 James Le Cuirot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-05 22:19 [gentoo-commits] repo/gentoo:master commit in: dev-util/uglifyjs/ James Le Cuirot
2024-08-15 21:21 James Le Cuirot
2024-06-19 21:51 James Le Cuirot
2024-01-20 22:21 James Le Cuirot
2022-10-29 13:22 James Le Cuirot
2022-10-29 13:22 James Le Cuirot
2022-10-08 12:59 James Le Cuirot
2022-10-08 12:59 James Le Cuirot
2022-09-26 21:01 James Le Cuirot
2022-09-21 20:52 James Le Cuirot
2022-09-21 20:52 James Le Cuirot
2022-08-29 12:49 Jakov Smolić
2022-08-18 22:59 James Le Cuirot
2022-08-18 22:21 James Le Cuirot
2022-07-27 22:35 James Le Cuirot
2022-07-06  6:06 Sam James
2022-07-05 22:10 James Le Cuirot
2022-06-22 21:50 James Le Cuirot
2022-06-11 10:51 James Le Cuirot
2022-04-10 21:39 James Le Cuirot
2022-03-13 22:42 James Le Cuirot
2022-02-26 23:44 James Le Cuirot
2022-02-13 13:54 James Le Cuirot
2022-01-29 22:25 James Le Cuirot
2021-12-15 23:47 James Le Cuirot
2021-11-03  9:30 James Le Cuirot
2021-09-11 10:11 James Le Cuirot
2021-09-01 20:52 James Le Cuirot

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=1652603389.01949003a47c8b08f24f9037cf3ab587c529ec71.chewi@gentoo \
    --to=chewi@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