From: Mark Goodwin <markgw@sgi.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs open questions
Date: Wed, 28 Jan 2009 20:30:58 +1100 [thread overview]
Message-ID: <498025D2.1060706@sgi.com> (raw)
In-Reply-To: <200901280937.23743@zmi.at>
Michael Monnerie wrote:
> On Dienstag 27 Januar 2009 Eric Sandeen wrote:
>> I'd love to be able to update these pdf files, but despite asking for
>> the source document several times over a couple months, nothing has
>> been provided. Unfortunately 'til then it's up to SGI to update them
>> and the community can't help much (SGI: hint, hint).
it's (finally) on the Open Source Review Board meeting agenda
for tomorrow (6am in my TZ :) I expect to release the src docs
shortly after that; the oss release process is time consuming.
> SGI, do you read that? Your users want to do your work, you should be
> happy 'bout that!
yes certainly, thanks.
Cheers
-- Mark
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-28 9:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 8:28 xfs open questions Michael Monnerie
2009-01-27 13:58 ` Eric Sandeen
2009-01-28 8:37 ` Michael Monnerie
2009-01-28 9:30 ` Mark Goodwin [this message]
2009-01-28 15:10 ` Eric Sandeen
2009-01-29 5:27 ` Mark Goodwin
2009-01-29 22:39 ` Christoph Hellwig
2009-01-28 17:04 ` Christoph Hellwig
2009-01-27 23:03 ` Michael Monnerie
2009-01-28 4:16 ` Russell Cattelan
2009-01-28 8:52 ` Michael Monnerie
2009-01-28 14:52 ` Russell Cattelan
2009-01-28 15:09 ` Russell Cattelan
2009-01-28 20:22 ` invalidated gpg signatures (was: Re: xfs open questions) Martin Steigerwald
2009-01-28 20:37 ` Iustin Pop
2009-01-28 22:44 ` Martin Steigerwald
2009-01-29 18:01 ` Michael Monnerie
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=498025D2.1060706@sgi.com \
--to=markgw@sgi.com \
--cc=michael.monnerie@is.it-management.at \
--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