From: Dave Chinner <david@fromorbit.com>
To: Martin Papik <mp6058@gmail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: XFS filesystem claims to be mounted after a disconnect
Date: Sat, 3 May 2014 09:38:23 +1000 [thread overview]
Message-ID: <20140502233823.GF26353@dastard> (raw)
In-Reply-To: <5363F22E.2060404@gmail.com>
On Fri, May 02, 2014 at 10:29:50PM +0300, Martin Papik wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
>
> > We have a lot of docs at
> > http://xfs.org/index.php/XFS_Papers_and_Documentation in
> > publican/xml format, but Dave has been making noises about
> > converting that to asciidoc. In any case, the goal is
> > documentation which is readily available, version-controlled, for
> > which patches may be submitted...
>
> Unless this documentation is part of the installable package, its
> utility is limited. My expectation was for the manual pages to be the
> reference. There could be a snippet in each man page saying "for more
> information go to http://....", which would help locate this
> additional documentation. :-)
Eventually it will become exactly that - an installable XFS
documentation package that ends up in /usr/share/doc/xfs. Other
parts of it will end up as the source for the wiki pages e.g. the
FAQ. As I do stuff, it ends up here:
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-documentation.git
But right now it's time and resources that limit the conversion and
development of that repository, so don't hold your breathe too long
waiting for it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-02 23:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 13:47 XFS filesystem claims to be mounted after a disconnect Martin Papik
2014-05-02 15:04 ` Eric Sandeen
2014-05-02 15:07 ` Eric Sandeen
2014-05-02 15:44 ` Mark Tinguely
2014-05-02 16:26 ` Martin Papik
2014-05-02 16:44 ` Martin Papik
2014-05-02 16:53 ` Eric Sandeen
2014-05-02 17:54 ` Martin Papik
2014-05-02 18:39 ` Eric Sandeen
2014-05-02 19:07 ` Martin Papik
2014-05-02 19:16 ` Eric Sandeen
2014-05-02 19:29 ` Martin Papik
2014-05-02 23:38 ` Dave Chinner [this message]
2014-05-02 23:35 ` Dave Chinner
2014-05-03 0:04 ` Martin Papik
2014-05-03 3:02 ` Dave Chinner
2014-06-02 11:22 ` Martin Papik
2014-06-02 23:41 ` Dave Chinner
2014-06-03 9:23 ` Martin Papik
2014-06-03 9:55 ` Stefan Ring
2014-06-03 10:48 ` Martin Papik
2014-06-03 21:28 ` Dave Chinner
2014-06-03 22:37 ` Martin Papik
2014-06-05 0:55 ` Dave Chinner
2014-06-05 1:38 ` Martin Papik
2014-06-05 19:39 ` Martin Papik
2014-06-05 22:41 ` Dave Chinner
2014-06-06 0:47 ` Martin Papik
2014-06-03 22:58 ` Martin Papik
2014-06-05 0:08 ` Dave Chinner
2014-06-05 1:07 ` Martin Papik
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=20140502233823.GF26353@dastard \
--to=david@fromorbit.com \
--cc=mp6058@gmail.com \
--cc=sandeen@sandeen.net \
--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;
as well as URLs for NNTP newsgroup(s).