public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: 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>,
	xfs-dev <xfs-dev@sgi.com>, Tony Ernst <tee@sgi.com>,
	Ric Wheeler <rwheeler@redhat.com>
Subject: Re: IMPORTANT: XFS Documentation
Date: Thu, 05 Feb 2009 16:27:05 -0600	[thread overview]
Message-ID: <498B67B9.3020505@sandeen.net> (raw)
In-Reply-To: <4989F4C2.3030305@sgi.com>

Mark Goodwin wrote:
> 
> 
> Sorry for the delay - the lawyers were pondering the GNU FDL Vrs the
> Creative Commons license (and settled on the latter). So now that's 
> resolved,
> I've updated the copyrights in the doc sources and put them in a git tree:
> 
> 	git://oss.sgi.com/xfs/cmds/xfsdocs.git
> 
> This repository is XFS group writable on oss.sgi.com. The directory 
> structure
> corresponds to (a subset of) the internal ptools tree below 
> xfs-cmds/xfsdocs.
> Since the files in this repository are binary, you'll need to co-ordinate
> check-out/check-in to avoid merge failures (git handles binaries but 
> can't merge
> them). I think Eric and/or others inside Redhat will have the first go 
> at it :)
> I also regenerated the PDFs and committed them too since they're also 
> present
> in the internal ptools tree.


Mark, John, & SGI - thanks for doing this, getting good docs out under a
license like this should allow them to continue to be relevant living
documents, and will add to the vitality of XFS in the future, I'm sure.
 Now of course I'll need to step up and contribute some updates.  :)

Thanks,

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2009-02-05 22:27 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
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 [this message]

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=498B67B9.3020505@sandeen.net \
    --to=sandeen@sandeen.net \
    --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