Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_bmap\s+\&\s+XML\s+patch\s*$/: 9 ]

Total 9 documents matching your query.

1. ite (score: 1): Author: monkeyiq <monkeyiq@xxxxxxxxxxxxxxxxxxxxx>; Date: Mon, 11 Feb 2002 23:22:00 +1000; With this little change one can use $ ./xfs_bmap -x ~/tmp/holes <?xml version="1.0"?> <extentlist> <extent id="0" type="hole" blocks="192" file-offset-start="0" file-offset-end="191" > </extent> <ex; /archives/xfs/2002-02/msg00192.html (8,206 bytes)
2. ite (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Tue, 12 Feb 2002 09:51:58 +1100; Now that I've seen the code, it seems this could be done with a 4/5 line perl/awk script which parses `xfs_bmap -vv /tmp/foo` rather than modifying the existing program at all. Thoughts? xfs_bmap ou; /archives/xfs/2002-02/msg00231.html (8,490 bytes)
3. +MD (score: 1): Author: monkeyiq <monkeyiq@xxxxxxxxxxxxxxxxxxxxx>; Date: Tue, 12 Feb 2002 09:31:27 +1000; Well, the main reason I was adding this was to avoid parsing output to get output, though that is very possible. I dont see that the script would be that much simpler than the xml output function by; /archives/xfs/2002-02/msg00233.html (9,469 bytes)
4. TP site (score: 1): Author: >; Date: Mon, 11 Feb 2002 23:22:00 +1000; /archives/xfs/2002-02/msg00766.html (8,206 bytes)
5. TP site (score: 1): Author: >; Date: Tue, 12 Feb 2002 09:51:58 +1100; /archives/xfs/2002-02/msg00805.html (8,490 bytes)
6. +LVM+MD (score: 1): Author: >; Date: Tue, 12 Feb 2002 09:31:27 +1000; /archives/xfs/2002-02/msg00807.html (9,469 bytes)
7. xfs_bmap & XML patch (score: 1): Author: monkeyiq <monkeyiq@xxxxxxxxxxxxxxxxxxxxx>; Date: Mon, 11 Feb 2002 23:22:00 +1000; Hi, With this little change one can use $ ./xfs_bmap -x ~/tmp/holes <?xml version="1.0"?> <extentlist> <extent id="0" type="hole" blocks="192" file-offset-start="0" file-offset-end="191" > </extent>; /archives/xfs/2002-02/msg01340.html (8,221 bytes)
8. Re: xfs_bmap & XML patch (score: 1): Author: Nathan Scott <nathans@xxxxxxx>; Date: Tue, 12 Feb 2002 09:51:58 +1100; hi, Now that I've seen the code, it seems this could be done with a 4/5 line perl/awk script which parses `xfs_bmap -vv /tmp/foo` rather than modifying the existing program at all. Thoughts? xfs_bmap; /archives/xfs/2002-02/msg01379.html (8,600 bytes)
9. Re: xfs_bmap & XML patch (score: 1): Author: monkeyiq <monkeyiq@xxxxxxxxxxxxxxxxxxxxx>; Date: Tue, 12 Feb 2002 09:31:27 +1000; Well, the main reason I was adding this was to avoid parsing output to get output, though that is very possible. I dont see that the script would be that much simpler than the xml output function by; /archives/xfs/2002-02/msg01381.html (9,484 bytes)

Current List: 1 - 9
Page: [1]