cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Orphaned bits in CVS HEAD.
Date: Wed, 29 Aug 2007 07:25:06 +0200	[thread overview]
Message-ID: <46D50332.8090906@ubuntu.com> (raw)


Hi guys,

not too long ago we discussed about removing unused bits from CVS HEAD tree.
Some cleaning has been already done.

These are files/dirs that are still in the tree but somewhat unused (yes some of
them have been discussed over and over but I am readding them here just to keep
a full overview):

clumon/ - this is now in conga and didn't receive any update in CVS HEAD for a
long time. The core code is the same as in RHEL5 branch. Like we agreed for
cs-deploy-tools, I think this can go from HEAD and live in RHEL5 for historical
reasons.

cmirror/Makefile - the entire userland tree is empty and it has been maintained
only in specific RHEL branches.

cmirror-kernel/* - it has been maintained only in specific RHEL branches. The
version in HEAD did not received a commit in months. The tree will move to
another kernel tree or catch up (or so I am told).

csnap*/ are in a similar situation as cmirror*/

fence/agents/apc/ has fence_apc.pl, fence_apc_snmp.py, powernet369.mib and
README files that looks obsoleted to me. If they are still required we should
probably make them available to the user in an easy way.

fence/agents/drac/test_drac.sh is this file still used for testing or is it
obsoleted?

gfs-kernel/patches/lock_dlm-include.patch seems unrequired.

gfs2/debug is not build or updated. I asked about it a few days back but no
comment so far. If it's still useful, please let me know and I will update the
relevant Makefiles to build and make it available.

gfs and gfs2 tools/ have decipher_lockstate_dump and parse_lockdump scripts.
Should we ship them or is it best to keep them only internal? on the note..
parse_lockdump is the same in both dirs.

Cheers
Fabio

-- 
I'm going to make him an offer he can't refuse.



             reply	other threads:[~2007-08-29  5:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29  5:25 Fabio Massimo Di Nitto [this message]
2007-08-29 13:29 ` [Cluster-devel] Orphaned bits in CVS HEAD Ryan McCabe
2007-08-29 18:31   ` Fabio M. Di Nitto
2007-08-29 19:56     ` Ryan McCabe

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=46D50332.8090906@ubuntu.com \
    --to=fabbione@ubuntu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).