All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.03-3-ge879971
Date: Tue, 3 Jun 2008 08:52:22 -0500	[thread overview]
Message-ID: <20080603135222.GA17147@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806030854380.5892@trider-g7>

On Tue, Jun 03, 2008 at 08:55:49AM +0200, Fabio M. Di Nitto wrote:
> On Mon, 2 Jun 2008, Joel Becker wrote:
> 
> >On Tue, Jun 03, 2008 at 05:57:35AM -0000, fabbione at sourceware.org wrote:
> >>commit e879971090c6821bb966f17875874d11aa740a5c
> >>Author: Fabio M. Di Nitto <fdinitto@redhat.com>
> >>Date:   Tue Jun 3 07:54:37 2008 +0200
> >>
> >>    [MISC] Make several API's private again
> >>
> >>    A bunch of API's have been exported and made public by mistake.
> >>
> >>    libdlmcontrol, libfenced and libgfscontrol are now private again
> >>    and no shared libraries are available.
> >
> >	Um, is libdlmcontrol the method by which fs control daemons
> >interact with dlm_controld?  If so, ocfs2_controld certainly needs that
> >shared library.
> 
> As long as David is ok with it.. i was explicitly told that those 
> libraries are for internal use only.
> 
> David can we make a final call on those libs?

Yes, libdlmcontrol is meant to be usd by ocfs2_controld.  I still think it
needs to be kept "private", or "internal" in some way to prevent someone
from trying to use it.



  reply	other threads:[~2008-06-03 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  5:57 [Cluster-devel] Cluster Project branch, master, updated. cluster-2.99.03-3-ge879971 fabbione
2008-06-03  6:42 ` Joel Becker
2008-06-03  6:55   ` Fabio M. Di Nitto
2008-06-03 13:52     ` David Teigland [this message]
2008-06-03 15:22       ` Fabio M. Di Nitto
2008-06-03 15:43         ` Joel Becker

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=20080603135222.GA17147@redhat.com \
    --to=teigland@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.