public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Klaus Strebel <klaus.strebel@gmx.net>
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: Sun, 19 Apr 2009 22:55:11 +0200	[thread overview]
Message-ID: <49EB8FAF.9060006@gmx.net> (raw)
In-Reply-To: <49E8D28F.9000500@tlinx.org>

Linda A. Walsh schrieb:
> Nathan Scott wrote:
>>>     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
> ---
>     Those are files from the actual utilities?  I.e. the
> source code for the utilities is stored in the kernel tree?  That the
> support routines for the utilities have changes doesn't imply that
> one would expect to find source-changes for the utils there unless
> the utils are in the kernel tree -- but I don't think so(?)  Like the
> 'util-linux' utils, I have the impression they are stored outside of
> the kernel tree.
>
>     No need to answer to tell me the util sources are not stored
> in the kernel (if that's the case), as that's my current "world view" 
> :-).
> But if I need to update my current world view (again), I hope you'll
> _gently_ let me know. :-)
>
Hi Linda,

your misunderstanding, git.kernel.org is a site where several git 
repositories are hosted, no the kernel source tree ;-). The 
fs/xfs/xxx.git is the path of the git-repository of the xfs-tools, i 
doesn't mean it's in the kernel source in the directory fs/xfs ...
Even the sources for ext2 ( 3, 4 ), btrfs, jfs, reiserfs et al. are not 
part of the Linux source tree, so what made you thinking that?

Cheers
Klaus

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

  reply	other threads:[~2009-04-19 20:55 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 ` getting changes (fixes or enhancements) to xfs-tools Nathan Scott
2009-04-17 19:03   ` Linda A. Walsh
2009-04-19 20:55     ` Klaus Strebel [this message]
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=49EB8FAF.9060006@gmx.net \
    --to=klaus.strebel@gmx.net \
    --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