From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>,
Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: xfs open questions
Date: Thu, 29 Jan 2009 17:39:29 -0500 [thread overview]
Message-ID: <20090129223929.GA20346@infradead.org> (raw)
In-Reply-To: <49813E27.9010309@sgi.com>
On Thu, Jan 29, 2009 at 04:27:03PM +1100, Mark Goodwin wrote:
> doc & ppt binary formats. My first thought was another git repository at
> git://oss/xfs/cmds/xfsdocs.git which would also include the web site html
> content. But doc and ppt binary files apparently always result in git merge
> conflicts (can't be patched) ... thoughts? Perhaps convert the content
> to wiki or maybe html and manage changes that way?
Better a git with merge conflicts than no SCM at all. So let's get it
out and into the new xfsdocs.git repo ASAP, and we'll see if we can
convert it to a more open format later.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-29 22:40 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
2009-01-28 15:10 ` Eric Sandeen
2009-01-29 5:27 ` Mark Goodwin
2009-01-29 22:39 ` Christoph Hellwig [this message]
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=20090129223929.GA20346@infradead.org \
--to=hch@infradead.org \
--cc=markgw@sgi.com \
--cc=michael.monnerie@is.it-management.at \
--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