From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-tex/minted/
Date: Thu, 3 Dec 2015 12:49:40 +0000 (UTC) [thread overview]
Message-ID: <1449146979.7f5e120c432b5fa3a02e5b2ec8c82a38ed5272ba.jlec@gentoo> (raw)
commit: 7f5e120c432b5fa3a02e5b2ec8c82a38ed5272ba
Author: Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 3 12:49:28 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Thu Dec 3 12:49:39 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f5e120c
dev-tex/minted: Fix bad merge
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=567448
Package-Manager: portage-2.2.25
Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>
dev-tex/minted/minted-1.7.ebuild | 4 ----
dev-tex/minted/minted-2.0.ebuild | 4 ----
2 files changed, 8 deletions(-)
diff --git a/dev-tex/minted/minted-1.7.ebuild b/dev-tex/minted/minted-1.7.ebuild
index 3e4ed32..0331cba 100644
--- a/dev-tex/minted/minted-1.7.ebuild
+++ b/dev-tex/minted/minted-1.7.ebuild
@@ -6,11 +6,7 @@ EAPI=5
inherit latex-package
-<<<<<<< 1b4109b06fe34ac39f3fc55996d66a9b6cc8d809
DESCRIPTION="LaTeX package for source code syntax highlighting"
-=======
-DESCRIPTION="Expressive syntax highlighting in using the powerful Pygments library"
->>>>>>> dev-tex/minted: Chop DESCRIPTION to 80 chars
HOMEPAGE="https://code.google.com/p/minted/"
SRC_URI="https://minted.googlecode.com/files/${PN}-v${PV}.zip"
diff --git a/dev-tex/minted/minted-2.0.ebuild b/dev-tex/minted/minted-2.0.ebuild
index a72ed11..07ed452 100644
--- a/dev-tex/minted/minted-2.0.ebuild
+++ b/dev-tex/minted/minted-2.0.ebuild
@@ -6,11 +6,7 @@ EAPI=5
inherit latex-package
-<<<<<<< 1b4109b06fe34ac39f3fc55996d66a9b6cc8d809
DESCRIPTION="LaTeX package for source code syntax highlighting"
-=======
-DESCRIPTION="Expressive syntax highlighting in using the powerful Pygments library"
->>>>>>> dev-tex/minted: Chop DESCRIPTION to 80 chars
HOMEPAGE="https://github.com/gpoore/minted"
SRC_URI="https://github.com/gpoore/minted/archive/v${PV}.tar.gz -> ${P}.tar.gz"
next reply other threads:[~2015-12-03 12:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 12:49 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 14:48 [gentoo-commits] repo/gentoo:master commit in: dev-tex/minted/ Arthur Zamarin
2025-02-07 14:44 Arthur Zamarin
2024-12-12 17:03 Florian Schmaus
2024-12-11 8:49 Florian Schmaus
2024-12-11 8:49 Florian Schmaus
2024-12-10 14:58 Florian Schmaus
2024-12-09 10:26 Florian Schmaus
2024-07-11 2:40 Ionen Wolkens
2024-06-21 15:47 Florian Schmaus
2024-06-21 15:47 Florian Schmaus
2024-06-21 4:23 Arthur Zamarin
2024-06-20 15:07 Ionen Wolkens
2024-06-14 17:29 Sam James
2024-06-14 17:29 Sam James
2024-06-14 17:20 Sam James
2024-06-14 17:20 Sam James
2024-06-14 14:42 Arthur Zamarin
2024-05-28 18:23 Arthur Zamarin
2024-05-26 6:06 Arthur Zamarin
2024-02-12 13:46 Jakov Smolić
2024-02-11 12:03 Sam James
2024-02-11 12:03 Sam James
2024-02-11 10:54 Florian Schmaus
2024-01-06 9:02 Sam James
2022-12-20 10:08 Maciej Barć
2022-12-19 22:28 Maciej Barć
2017-05-25 21:15 Patrice Clement
2017-05-25 21:12 Patrice Clement
2016-12-26 21:22 Kacper Kowalik
2016-03-11 16:17 Patrice Clement
2015-12-03 10:21 Justin Lecher
2015-12-03 10:11 Guilherme Amadio
2015-12-03 10:11 Guilherme Amadio
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=1449146979.7f5e120c432b5fa3a02e5b2ec8c82a38ed5272ba.jlec@gentoo \
--to=jlec@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