From: Ian Stakenvicius <axs@gentoo.org>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] About using a CONFIGURATION (or SETUP) file under /usr/share/doc for configuration information
Date: Sat, 12 Jan 2013 07:54:54 -0500 [thread overview]
Message-ID: <F9F76ED4-199A-4703-A9F7-D1A06BD0BD13@gentoo.org> (raw)
In-Reply-To: <50F15BCA.4040001@gentoo.org>
On 2013-01-12, at 7:49 AM, Zac Medico <zmedico@gentoo.org> wrote:
>
> Still, it maybe it would be reasonable to use a different
> README.gentoo for each SLOT, it there's more than one?
especially since that means no special logic is necessary when cleaning them up on uninstall...
next prev parent reply other threads:[~2013-01-12 12:55 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 9:26 [gentoo-dev] About using a CONFIGURATION (or SETUP) file under /usr/share/doc for configuration information Pacho Ramos
2012-12-22 15:05 ` Amadeusz Żołnowski
2012-12-22 16:18 ` Brian Dolbec
2012-12-22 21:46 ` Markos Chandras
2012-12-22 21:53 ` Zac Medico
2012-12-23 0:16 ` Markos Chandras
2012-12-23 9:57 ` Pacho Ramos
2012-12-23 12:20 ` Markos Chandras
2012-12-23 13:58 ` Alexandre Rostovtsev
2012-12-23 15:10 ` Markos Chandras
2012-12-23 16:35 ` Brian Dolbec
2012-12-23 21:36 ` Zac Medico
2012-12-23 22:54 ` Pacho Ramos
2012-12-23 23:17 ` Diego Elio Pettenò
2012-12-23 23:30 ` Pacho Ramos
2012-12-29 23:09 ` Pacho Ramos
2012-12-29 23:20 ` Alexander Berntsen
2012-12-31 13:21 ` Pacho Ramos
2012-12-31 22:53 ` Zac Medico
2013-01-01 13:32 ` Pacho Ramos
2013-01-01 13:39 ` Pacho Ramos
2013-01-02 0:01 ` Zac Medico
2013-01-02 11:48 ` Pacho Ramos
2013-01-02 12:00 ` Zac Medico
2012-12-23 9:54 ` Pacho Ramos
2013-01-05 5:34 ` Donnie Berkholz
2013-01-06 4:24 ` William Hubbs
2013-01-06 9:04 ` Ralph Sennhauser
2013-01-07 1:30 ` Zac Medico
2013-01-07 1:36 ` Michael Mol
2013-01-07 1:54 ` Zac Medico
2013-01-08 1:35 ` Michael Mol
2013-01-08 1:56 ` Zac Medico
2013-01-07 4:08 ` [gentoo-dev] " Duncan
2013-01-07 9:34 ` [gentoo-dev] " Pacho Ramos
2013-01-07 19:46 ` Amadeusz Żołnowski
2013-01-08 1:17 ` Zac Medico
2013-01-09 19:53 ` Pacho Ramos
2013-01-09 20:04 ` Zac Medico
2013-01-09 21:15 ` Pacho Ramos
2013-01-09 21:29 ` Pacho Ramos
2013-01-12 9:46 ` Pacho Ramos
2013-01-12 10:01 ` Zac Medico
2013-01-12 10:34 ` Pacho Ramos
2013-01-12 10:55 ` Pacho Ramos
2013-01-12 12:49 ` Zac Medico
2013-01-12 12:54 ` Ian Stakenvicius [this message]
2013-01-13 12:18 ` Pacho Ramos
2013-01-13 12:54 ` Zac Medico
2013-01-13 12:59 ` Pacho Ramos
2013-01-14 9:29 ` Zac Medico
2013-01-17 15:17 ` Pacho Ramos
2013-01-17 15:47 ` Zac Medico
2013-01-17 16:00 ` Pacho Ramos
2013-01-17 16:31 ` Zac Medico
2013-01-20 11:43 ` Pacho Ramos
2013-01-17 16:54 ` Ian Stakenvicius
2013-01-17 17:02 ` Pacho Ramos
2013-01-17 17:11 ` Ian Stakenvicius
2013-01-17 18:37 ` Pacho Ramos
2013-01-17 16:47 ` Ciaran McCreesh
2013-01-17 17:14 ` Ian Stakenvicius
2013-01-17 17:15 ` Ciaran McCreesh
2013-01-17 17:25 ` [gentoo-dev] in-place SLOT updates on ebuilds? Ian Stakenvicius
2013-01-17 17:30 ` Ciaran McCreesh
2013-01-17 17:43 ` Ian Stakenvicius
2013-01-17 17:57 ` [gentoo-dev] About using a CONFIGURATION (or SETUP) file under /usr/share/doc for configuration information Zac Medico
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=F9F76ED4-199A-4703-A9F7-D1A06BD0BD13@gentoo.org \
--to=axs@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