public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donny Davies <woodchip@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Policy violation possible (concerns openldap/nss_ldap)
Date: Wed, 18 Jun 2003 14:18:08 -0400	[thread overview]
Message-ID: <20030618181808.GA13853@breccia.escarpment> (raw)
In-Reply-To: <871xxrb84d.fsf@nb-acer.better-com.de>

[snip]
>Have the changes described above to be reported as bug in nss_ldap?
>
>How can we ensure the integrity of conf-files used by more than one
>package when different packages use different locations for the *same*
>configuration (a bad thing anyway)?

Martin,

  I've already filed one:  http://bugs.gentoo.org/show_bug.cgi?id=22906

        Donny.


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-18 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 17:36 [gentoo-dev] Policy violation possible (concerns openldap/nss_ldap) Martin Lesser
2003-06-18 18:18 ` Donny Davies [this message]
2003-06-19 17:55 ` [gentoo-dev] " paul
2003-06-19 15:42   ` Donny Davies

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=20030618181808.GA13853@breccia.escarpment \
    --to=woodchip@gentoo.org \
    --cc=gentoo-dev@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