From: Joshua Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites for net-dns/ldapdns
Date: Fri, 25 Dec 2009 07:00:22 -0800 [thread overview]
Message-ID: <20091225070022.1ef8e99b@angelstorm> (raw)
In-Reply-To: <20091223104006.10d6d564@dante>
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
On Wed, 23 Dec 2009 10:40:06 -0600
Victor Ostorga <vostorga@gentoo.org> wrote:
>
> # Víctor Ostorga <vostorga@gentoo.org> (23 Dec 2009)
> # Last bump in 2005, does not build against current
> # stable net-nds/openldap-2.4.19-r1 bug #247956
> # Removal in 30 days
> net-dns/ldapdns
>
So what about http://www.gentoo.org/doc/en/ldapdns-guide.xml -- you want the GDP to just remove the doc? We can do that.
Is there a compatible drop-in replacement that will allow us to s/ldapdns/foo throughout the guide?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-25 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 16:40 [gentoo-dev] Last rites for net-dns/ldapdns Victor Ostorga
2009-12-25 15:00 ` Joshua Saddler [this message]
2009-12-26 5:47 ` Victor Ostorga
2009-12-26 7:42 ` Mario Fetka (geos_one)
2009-12-26 14:19 ` Joshua Saddler
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=20091225070022.1ef8e99b@angelstorm \
--to=nightmorph@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