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: dev-util/cargo-c/
Date: Sat, 27 May 2023 15:29:02 +0000 (UTC)	[thread overview]
Message-ID: <1685200973.16e434fe89ed6a46d7d491fd21571249e7237bf7.sam@gentoo> (raw)

commit:     16e434fe89ed6a46d7d491fd21571249e7237bf7
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat May 27 15:22:53 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat May 27 15:22:53 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=16e434fe

dev-util/cargo-c: fix DoubleEmptyLine

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-util/cargo-c/cargo-c-0.9.16.ebuild | 1 -
 1 file changed, 1 deletion(-)

diff --git a/dev-util/cargo-c/cargo-c-0.9.16.ebuild b/dev-util/cargo-c/cargo-c-0.9.16.ebuild
index 5d22ec5e499e..8f9f54e26600 100644
--- a/dev-util/cargo-c/cargo-c-0.9.16.ebuild
+++ b/dev-util/cargo-c/cargo-c-0.9.16.ebuild
@@ -195,7 +195,6 @@ fi
 
 SRC_URI+=" $(cargo_crate_uris)"
 
-
 LICENSE="0BSD Apache-2.0 Apache-2.0-with-LLVM-exceptions Boost-1.0 MIT MPL-2.0 Unlicense ZLIB"
 SLOT="0"
 KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"


             reply	other threads:[~2023-05-27 15:29 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 15:29 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-05 18:18 [gentoo-commits] repo/gentoo:master commit in: dev-util/cargo-c/ Luca Barbato
2024-06-21  9:16 Luca Barbato
2024-05-12 12:17 Luca Barbato
2024-03-23 13:19 Luca Barbato
2024-03-22 16:33 Arthur Zamarin
2024-03-21  7:24 Ionen Wolkens
2024-03-04  7:43 Sam James
2024-03-04  7:43 Sam James
2024-03-04  7:43 Sam James
2024-03-04  7:43 Sam James
2024-03-04  7:43 Sam James
2024-03-04  7:43 Sam James
2024-03-04  5:47 Sam James
2024-03-02  5:05 Sam James
2024-02-11 20:53 Luca Barbato
2024-01-03 22:20 Luca Barbato
2023-11-21  9:41 Luca Barbato
2023-10-16  9:53 Luca Barbato
2023-10-16  9:53 Luca Barbato
2023-08-27 15:11 Luca Barbato
2023-08-10 21:24 Luca Barbato
2023-07-20 10:16 WANG Xuerui
2023-07-18 19:46 Luca Barbato
2023-06-13 17:29 Sam James
2023-06-04 13:29 Luca Barbato
2023-05-03  8:59 Sam James
2023-05-03  8:59 Sam James
2023-05-03  7:49 Sam James
2023-02-22  9:55 Luca Barbato
2023-01-13 19:38 Arthur Zamarin
2022-12-27 19:42 Luca Barbato
2022-12-25 21:24 Sam James
2022-12-18 19:02 Arthur Zamarin
2022-12-18 12:12 Sam James
2022-12-18 12:12 Sam James
2022-11-29 14:49 Luca Barbato
2022-11-22 18:46 Arthur Zamarin
2022-11-18  5:30 Sam James
2022-10-20 18:36 Georgy Yakovlev
2022-10-10 14:31 Luca Barbato
2022-09-06 21:41 Sam James
2022-08-26 13:20 Arthur Zamarin
2022-08-26 10:27 Sam James
2022-08-14  7:46 Luca Barbato
2022-07-27 20:36 Luca Barbato
2022-05-13 17:41 Luca Barbato
2022-02-22  3:37 Sam James
2021-12-25 17:41 Arthur Zamarin
2021-12-25 17:31 Arthur Zamarin
2021-12-25 17:29 Arthur Zamarin
2021-12-25  8:25 Agostino Sarubbo
2021-12-25  8:24 Agostino Sarubbo
2021-12-24  7:08 Sam James
2021-12-24  6:46 Sam James
2021-12-24  6:45 Sam James
2021-12-24  6:45 Sam James
2021-10-26 12:09 Luca Barbato
2021-09-23 10:30 Luca Barbato
2021-09-17 10:16 Luca Barbato
2021-08-18 20:02 Sam James
2021-08-18 20:02 Sam James
2021-08-02 12:33 Marek Szuba
2021-07-03 11:00 Luca Barbato
2021-06-19  2:10 Sam James
2021-05-16 18:41 Luca Barbato
2021-05-02 17:56 Mikle Kolyada
2021-04-02 18:19 Luca Barbato
2021-02-01  7:25 Luca Barbato
2021-01-13 17:03 Luca Barbato
2020-10-09  8:36 Agostino Sarubbo
2020-10-08  2:30 Sam James
2020-10-07 20:16 Sam James
2020-10-07 18:52 Sam James
2020-10-07 18:50 Sam James
2020-07-19 15:48 Sam James
2020-07-13 22:17 Georgy Yakovlev
2020-07-12  1:51 Sam James
2020-07-04 21:55 Mart Raudsepp
2020-04-04 15:43 Luca Barbato

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=1685200973.16e434fe89ed6a46d7d491fd21571249e7237bf7.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