From: "Alexis Ballier" <aballier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] dev/aballier:master commit in: /
Date: Wed, 27 Jul 2011 12:06:49 +0000 (UTC) [thread overview]
Message-ID: <07a6410a7d130f28d0bdbeaebcc9526823e4fa14.aballier@gentoo> (raw)
commit: 07a6410a7d130f28d0bdbeaebcc9526823e4fa14
Author: Alexis Ballier <aballier <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 27 12:00:26 2011 +0000
Commit: Alexis Ballier <aballier <AT> gentoo <DOT> org>
CommitDate: Wed Jul 27 12:00:26 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=dev/aballier.git;a=commit;h=07a6410a
Changes file was used when developping for TeX Live 2007 in the overlay... remove
---
Changes | 19 -------------------
1 files changed, 0 insertions(+), 19 deletions(-)
diff --git a/Changes b/Changes
deleted file mode 100644
index e2581f4..0000000
--- a/Changes
+++ /dev/null
@@ -1,19 +0,0 @@
-Changes in r129 :
-now texlive-module eclass builds and installs format files by itself rather than
-leaving fmtutil doing it. As a result you might have file collisions for files
-not owned by any package in /usr/share/texmf-var, just disable collision
-protection and it should be fine.
-
-
-
-
-
-For people already using the overlay, texlive-source has been renamed to
-texlive-core, it is recommended to remove texlive-source and install
-texlive-core.
-
-Copying texlive-source-2007.tar.bz2 as texlive-core-2007.tar.bz2 in your
-distfiles dir and regenerating texlive-core's digest should be all what is
-needed before migrating.
-
-Sorry for the inconvenience, hopefully there wont be any other name change.
next reply other threads:[~2011-07-27 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 12:06 Alexis Ballier [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-18 14:38 [gentoo-commits] dev/aballier:master commit in: / Alexis Ballier
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=07a6410a7d130f28d0bdbeaebcc9526823e4fa14.aballier@gentoo \
--to=aballier@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