All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Heads-up: retiring gfs_controld
Date: Sun, 17 Feb 2013 14:08:35 +0000	[thread overview]
Message-ID: <5120E463.4020208@redhat.com> (raw)
In-Reply-To: <511FB556.9070301@redhat.com>

On 16/02/13 16:35, Fabio M. Di Nitto wrote:
> On 02/15/2013 02:18 PM, Andrew Price wrote:
>> Hi,
>>
>> Now that Fedora 16 has EOL'd we have little reason to keep gfs_controld
>> and gfs_control in gfs2-utils. They're currently disabled by default but
>> can be enabled with configure option --enable-gfs_controld which adds
>> additional dependencies on corosynclib, clusterlib (discontinued) and
>> openaislib (discontinued).
>>
>> My intention is to remove gfs_control* from gfs2-utils.git before the
>> next release unless there are any good reasons to keep them around.
>>
>> Andy
>>
>
> Just make sure it is clear from which exact kernel version it is
> possible to operate without gfs_control*. so that maintainers will not
> try to backport to linux 1.0.
>
> Fabio

I'd have to get confirmation on this but it looks like this commit 
obsoleted gfs_controld:

    commit e0c2a9aa1e68455dc3439e95d85cabcaff073666
    Author: David Teigland <teigland@redhat.com>
    Date:   Mon Jan 9 17:18:05 2012 -0500

        GFS2: dlm based recovery coordination

        This new method of managing recovery is an alternative to
        the previous approach of using the userland gfs_controld.
    [...]

Which was released in:

    $ git describe --contains e0c2a9aa1e68455dc3439e95d85cabcaff073666
    v3.3-rc1~77^2~4

So a little while after linux 1.0 :)

Andy



      reply	other threads:[~2013-02-17 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 13:18 [Cluster-devel] Heads-up: retiring gfs_controld Andrew Price
2013-02-16 16:35 ` Fabio M. Di Nitto
2013-02-17 14:08   ` Andrew Price [this message]

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=5120E463.4020208@redhat.com \
    --to=anprice@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.