From: Nathan Scott <nscott@aconex.com>
To: bnaujok@sgi.com
Cc: xfs@oss.sgi.com
Subject: Recent changes in xfsprogs
Date: Wed, 06 Dec 2006 10:06:10 +1100 [thread overview]
Message-ID: <1165359970.1281.51.camel@edge> (raw)
Yo Barry,
xfsprogs/doc/CHANGES
- Rename include/list.h to xfs_list.h so that other applications
do not accidentally use it.
What was the problem here? This doesnt sound like the right fix -
there should be no applications outside of the XFS userspace that
use libxfs.h - thats what <xfs/xfs.h> is for (exactly this reason,
preventing namespace collision, by reducing all the XFS internals
being exposed).
Also, there seems to be lots of checkin mail not making it out to
oss.sgi.com (let alone review mail), making it difficult for people
to keep up to date with changes (and keep distros, like Debian,
uptodate) ... could y'all make some effort to keep us "on the
outside" in the loop?
Oh, noone is updating oss.sgi.com/projects/xfs/{news,index}.html
with recent changes either - seems like progress has come to a
halt to those of us no longer in the secret cabal, anyway ;) ...
just FYI.
cheers.
--
Nathan
next reply other threads:[~2006-12-05 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 23:06 Nathan Scott [this message]
2006-12-06 1:49 ` Recent changes in xfsprogs David Chatterton
2006-12-06 2:08 ` Nathan Scott
2006-12-06 22:08 ` Eric Sandeen
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=1165359970.1281.51.camel@edge \
--to=nscott@aconex.com \
--cc=bnaujok@sgi.com \
--cc=xfs@oss.sgi.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