public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-backup/untangle-https-backup/
Date: Fri,  5 Oct 2018 22:59:11 +0000 (UTC)	[thread overview]
Message-ID: <1538780286.bfb5b21a4b6b93fb0877138de29a716add315dd2.mjo@gentoo> (raw)

commit:     bfb5b21a4b6b93fb0877138de29a716add315dd2
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Fri Oct  5 22:58:06 2018 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Fri Oct  5 22:58:06 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bfb5b21a

app-backup/untangle-https-backup: new version 0.0.9.

Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.10

 app-backup/untangle-https-backup/Manifest                               | 2 +-
 ...gle-https-backup-0.0.8.ebuild => untangle-https-backup-0.0.9.ebuild} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/app-backup/untangle-https-backup/Manifest b/app-backup/untangle-https-backup/Manifest
index 396653013f6..b14f21a647d 100644
--- a/app-backup/untangle-https-backup/Manifest
+++ b/app-backup/untangle-https-backup/Manifest
@@ -1 +1 @@
-DIST untangle-https-backup-0.0.8.tar.gz 16263 BLAKE2B 3a41b2ee172a14e3a11ac6e1d47adf9bb818facf8e45d16826a0da70e9280c28d09f9d4f670b4efdda487c152ce4ef5350709b70165dc9262ae4e3e0d0a106c9 SHA512 4eb74d4cb939a9ac59fc475b5dbcc2a1fb4b36b59e6335c02b6de44b5fd56c44f1b7a52f6b71b36ed91663aff17556e0c9cfb04f309a191596a7a858ffec4693
+DIST untangle-https-backup-0.0.9.tar.gz 16371 BLAKE2B f111e75987a43ccde02643fbb13c956e8368fee95abc7ea63f5c1df3431a8c9b843b8c8f386ed7d7780fd456095903ae0e80036b4b3ea9f0bbe304034975f0f9 SHA512 71d13f289ef35736dd2dfda300ef518439169b43605ba7173982933be817d7e37070f1dd4c0282e82026d5dfcb70b8be1c75daa84d5d72f0b0a4621cf0e2a418

diff --git a/app-backup/untangle-https-backup/untangle-https-backup-0.0.8.ebuild b/app-backup/untangle-https-backup/untangle-https-backup-0.0.9.ebuild
similarity index 100%
rename from app-backup/untangle-https-backup/untangle-https-backup-0.0.8.ebuild
rename to app-backup/untangle-https-backup/untangle-https-backup-0.0.9.ebuild


             reply	other threads:[~2018-10-05 22:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 22:59 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-14 11:30 [gentoo-commits] repo/gentoo:master commit in: app-backup/untangle-https-backup/ Michael Orlitzky
2023-11-15  0:26 Michael Orlitzky
2023-04-19 12:35 Michael Orlitzky
2023-04-19 12:35 Michael Orlitzky
2023-02-25 17:07 Michael Orlitzky
2021-10-26  3:36 Michael Orlitzky
2021-10-26  3:12 Sam James
2021-08-21 13:37 Michael Orlitzky
2021-07-29 15:38 Michael Orlitzky
2020-05-12 10:36 Michael Orlitzky
2020-05-12 10:36 Michael Orlitzky
2020-04-19 23:30 Michael Orlitzky
2019-05-07  0:34 Michael Orlitzky
2018-10-06 21:16 Michael Orlitzky
2018-06-27 17:15 Pacho Ramos
2018-04-18  0:56 Michael Orlitzky
2017-10-23 23:54 Michael Orlitzky
2017-01-01 22:51 Michael Orlitzky
2017-01-01 22:17 Michael Orlitzky
2016-05-15 19:44 Michael Orlitzky

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=1538780286.bfb5b21a4b6b93fb0877138de29a716add315dd2.mjo@gentoo \
    --to=mjo@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