public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: getting changes (fixes or enhancements) to xfs-tools
Date: Thu, 16 Apr 2009 11:36:58 -0700	[thread overview]
Message-ID: <49E77ACA.9060301@tlinx.org> (raw)
In-Reply-To: <49E746A0.5020008@sandeen.net>

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.

     FWIW: I copied all 1327 entries to a text file and searched for
any string "xfs[a-z]" to search for any comments about utility changes.
Only strings found were for the daemons that are run.

     Now that I've determined that the xfs utils are not in the kernel
source tree (I wouldn't have expected them to be), maybe I can more
be less indirect and ask: Who is managing the the xfs_utils, Where are
they kept and What is the procedure for trying to get changes (fixes
or enhancements) to them?   (I prefer direct questioning, but too many
people, even in the engineering/sw community,  find it rude or abrupt,
so it's not usually my 1st choice).

In other words, does one:

(I) suggest new ideas and if the keeper(s) likes them, they are
     implemented and redistributed?
   OR
(II.1) suggest new ideas and see if keeper(s) approve of 'project' so
     one can then go and
     (i) implement the changes in a local version, and then?
     	(a) check them in?
           OR
         (b) submit for approval so they can be approved for
             inclusion (or fixing any found problems)
   OR
(III) just go off and implement the code, then come back and say, hey,
     here are my changes for this idea, and just expect to be greeted
     with open arms?  ;^/

---
(I hope I got the indentation and syntax correct in that, English
syntax isn't always the easiest language to express nested options
in...:-))

     I'm trying to get clear on process.  If they are in the kernel
tree, there may be no way for me to get from A->B, othewise, I'm
trying to find out where one might have hope of bouncing ideas that
might get implemented or that if sufficiently positively received
might spure someone to try implementing the changes themselves (and
possibly (and possibly get in completely over their head....or not.)

:-)
thanks!
-linda

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

  reply	other threads:[~2009-04-16 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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       ` Linda A. Walsh [this message]
2009-04-16 20:50         ` getting changes (fixes or enhancements) to xfs-tools Eric Sandeen
2009-04-16 21:15         ` Felix Blyakher
2009-04-16  6:05 ` future of xfs, oss.sgi.com after sgi purchased? Felix Blyakher
2009-04-16 15:54 ` Russell Cattelan
     [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

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=49E77ACA.9060301@tlinx.org \
    --to=xfs@tlinx.org \
    --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