From: Russell Cattelan <cattelan@thebarn.com>
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>, Tony Ernst <tee@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>, Gary Hagensen <gwh@sgi.com>,
Ric Wheeler <rwheeler@redhat.com>
Subject: Re: IMPORTANT: XFS Documentation
Date: Sun, 08 Feb 2009 18:53:05 -0600 [thread overview]
Message-ID: <498F7E71.8040600@xfs.org> (raw)
In-Reply-To: <498F7861.6010109@sgi.com>
Mark Goodwin wrote:
>
>
> Russell Cattelan wrote:
>> Christoph Hellwig wrote:
>> ...
>>>> I've updated the copyrights in the doc sources and put them in a
>>>> git tree:
>>>>
>>>> git://oss.sgi.com/xfs/cmds/xfsdocs.git
>>> Russell, can you add this to the list of repositories to be
>>> displayed on
>>>
>>> http://oss.sgi.com/cgi-bin/gitweb.cgi
>>
>> or maybe we should just update the existing xfs-website tree?
>> http://oss.sgi.com/cgi-bin/gitweb.cgi?p=cattelan/xfs-website/.git;a=summary
>>
>
> Rus, I didn't know that tree existed - it now has incorrect copyright
> notices for the doc sources. However, since it's ahead of ptools
> (and has cvs imported history too), I'll clone it as a replacement
> and then merge in the training docs with updated copyrights. It's easier
> for SGI if the official tree is git://oss.sgi.com/xfs/cmds/xfsdocs.git
> since the directory structure mirrors the internal ptools hierarchy,
> along with the other xfs/cmds trees.
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.
>
>>> Talking about that any chance you could convert your cvsimport
>>> repositories to bare repos like all the others on oss? And maybe
>>> move the old xfs-cmds import under cattelan/ like the other cvsimport
>>> ones?
>>>
>> I moved cvsimported xfs-import dmapi-import and xfs-cmds under archive.
>
> Thanks for that.
>
> Cheers
> -- Mark
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-09 0:53 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 [this message]
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
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=498F7E71.8040600@xfs.org \
--to=cattelan@thebarn.com \
--cc=gbeshers@sgi.com \
--cc=gwh@sgi.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.