public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: getting changes (fixes or enhancements) to xfs-tools
Date: Fri, 17 Apr 2009 07:28:37 +1000 (EST)	[thread overview]
Message-ID: <615709150.3493811239917317690.JavaMail.root@mail-au.aconex.com> (raw)
In-Reply-To: <907831127.3493791239917257256.JavaMail.root@mail-au.aconex.com>


----- "Linda A. Walsh" <xfs@tlinx.org> wrote:

> Eric Sandeen wrote:
> > Linda A. Walsh wrote:
> >> I can understand that for kernel work, but what about the xfs
> utils? 
> > Again, just look at the git logs.
> > -Eric
> ----
> 
>     I understand you want people to see the work that has gone into
> the
> kernel, but telling someone to search through 1327 entries just to
> find
> an answer of 'no', seems a bit ...something.

http://git.kernel.org/
    fs/xfs/xfsdump-dev.git
    fs/xfs/xfsprogs-dev.git
    fs/xfs/xfstests-dev.git
    fs/xfs/dmapi-dev.git

-- 
Nathan

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

       reply	other threads:[~2009-04-16 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <907831127.3493791239917257256.JavaMail.root@mail-au.aconex.com>
2009-04-16 21:28 ` Nathan Scott [this message]
2009-04-17 19:03   ` getting changes (fixes or enhancements) to xfs-tools Linda A. Walsh
2009-04-19 20:55     ` Klaus Strebel
2009-04-15 21:23 future of xfs, oss.sgi.com after sgi purchased? Linda A. Walsh
2009-04-16  4:41 ` Eric Sandeen
2009-04-16  8:34   ` Linda A. Walsh
2009-04-16 14:54     ` Eric Sandeen
2009-04-16 18:36       ` getting changes (fixes or enhancements) to xfs-tools Linda A. Walsh
2009-04-16 20:50         ` Eric Sandeen
2009-04-16 21:15         ` Felix Blyakher

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=615709150.3493811239917317690.JavaMail.root@mail-au.aconex.com \
    --to=nscott@aconex.com \
    --cc=xfs@oss.sgi.com \
    --cc=xfs@tlinx.org \
    /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