From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
SGI Engineering Interfaces to Red Hat <redhat-interface@sgi.com>,
Marizol Martinez <martinez@redhat.com>,
Gary Hagensen <gwh@sgi.com>, George Beshers <gbeshers@sgi.com>,
John Hesterberg <jh@sgi.com>, xfs-oss <xfs@oss.sgi.com>,
Christoph Hellwig <hch@infradead.org>,
Russell Cattelan <cattelan@thebarn.com>,
xfs-dev <xfs-dev@sgi.com>, Tony Ernst <tee@sgi.com>,
Ric Wheeler <rwheeler@redhat.com>
Subject: Re: IMPORTANT: XFS Documentation
Date: Tue, 10 Feb 2009 13:09:48 -0500 [thread overview]
Message-ID: <20090210180948.GA18457@infradead.org> (raw)
In-Reply-To: <498FD62D.9010604@sgi.com>
On Mon, Feb 09, 2009 at 06:07:25PM +1100, Mark Goodwin wrote:
>> That's cool, I'll change the web site to point to the new repo
>> once you have it fixed up.
>> Just trying to keep the clutter down.
>
> Ok, done
So now we have the old xfsdocs repo replaced by what essentially be
xfsweb.
I think we should have a clean repo for the document sources somewhere,
not intermindlged with the more or less dead website..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-10 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1231946704.3929.36.camel@localhost.localdomain>
[not found] ` <20090120160346.GJ17616@sgi.com>
[not found] ` <1232480744.23291.101.camel@localhost.localdomain>
[not found] ` <20090128202715.GR16689@sgi.com>
[not found] ` <1233175168.25011.155.camel@localhost.localdomain>
[not found] ` <20090204183603.GA26714@sgi.com>
2009-02-04 20:04 ` IMPORTANT: XFS Documentation Mark Goodwin
2009-02-05 11:29 ` Christoph Hellwig
2009-02-07 13:39 ` Russell Cattelan
2009-02-09 0:27 ` Mark Goodwin
2009-02-09 0:53 ` Russell Cattelan
2009-02-09 7:07 ` Mark Goodwin
2009-02-10 18:09 ` Christoph Hellwig [this message]
2009-02-10 18:24 ` Eric Sandeen
2009-02-10 20:35 ` Mark Goodwin
2009-02-10 20:37 ` Christoph Hellwig
2009-02-10 20:56 ` Mark Goodwin
2009-02-05 22:27 ` 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=20090210180948.GA18457@infradead.org \
--to=hch@infradead.org \
--cc=cattelan@thebarn.com \
--cc=gbeshers@sgi.com \
--cc=gwh@sgi.com \
--cc=jh@sgi.com \
--cc=markgw@sgi.com \
--cc=martinez@redhat.com \
--cc=redhat-interface@sgi.com \
--cc=rwheeler@redhat.com \
--cc=sandeen@redhat.com \
--cc=tee@sgi.com \
--cc=xfs-dev@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