From: Eric Sandeen <sandeen@sandeen.net>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs_fsr: XFS_IOC_SWAPEXT failed; & miscellania
Date: Tue, 20 Oct 2009 21:28:09 -0500 [thread overview]
Message-ID: <4ADE71B9.4000909@sandeen.net> (raw)
In-Reply-To: <4ADE710C.3020107@tlinx.org>
Linda A. Walsh wrote:
> Eric Sandeen wrote:
>> Linda A. Walsh asked:
>>> 4) is it possible to configure the xfs_utils with 'readline' and history
>>
>> current upstream has fixed readline support:
>>
>> d2e43158ae65863df2d5310381ed316f8e6871ce xfsprogs: fix
>> readline/editline for xfs_io and xfs_quota
>>
>> -Eric
>
> Excellent.
>
> If I have time, will have to figure out how to pull that down -- no
> telling when it
> will appear in my distro (of course no telling when it went into the
> upstream)...
> (Of course by the time I have the time, to do it, they may have it in
> there as
> well! :-)).
>
> Does upstream mean available via some publically available source
> retrieval?
> cvs, subversion, ... whatever xfs uses...?
>
> -l
>
yes, it's in the git tree.
http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfsprogs.git;a=commitdiff;h=d2e43158ae65863df2d5310381ed316f8e6871ce
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-10-21 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 5:41 xfs_fsr: XFS_IOC_SWAPEXT failed : busy?m Linda A. Walsh
2009-10-20 22:04 ` Eric Sandeen
2009-10-21 2:15 ` xfs_fsr: XFS_IOC_SWAPEXT failed; & miscellania Linda A. Walsh
2009-10-21 2:18 ` Eric Sandeen
2009-10-21 2:25 ` Linda A. Walsh
2009-10-21 2:28 ` Eric Sandeen [this message]
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=4ADE71B9.4000909@sandeen.net \
--to=sandeen@sandeen.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