From: Eric Sandeen <sandeen@sandeen.net>
To: Bogdan <bogdandr@op.pl>
Cc: xfs@oss.sgi.com
Subject: Re: xfsprogs: minimum version with these commands
Date: Sun, 29 Aug 2010 20:52:54 -0500 [thread overview]
Message-ID: <4C7B0EF6.5030505@sandeen.net> (raw)
In-Reply-To: <4C7A2654.3080106@op.pl>
Bogdan wrote:
> Hello.
>
> I couldn't find this information in the xfsprogs ChangeLog, so I'm
> asking here: what is the minimum version of xfsprogs to:
>
> 1) contain these utilities: xfs_db, xfs_freeze, xfs_check, and
> 2) xfs_db accepts the following command-line parameters: -i, -c, and
> 3) xfs_freeze accepts the following command-line parameters: -f, -u, and
> 4) xfs_db accepts the following interactive mode commands: "freesp
> -d", "quit", "blockget -n", "ncheck", "sb 0", "print".
I am not surprised that changelogs do not mention when "quit" was
added to xfs_db ...!
> Or is there a ChangeLog that covers all xfsprogs versions in such
> deatil that I would be able to find this myself? If so, where can I
> find it?
>
You could look at git and/or cvs history/blame to see when commands &
options were added.
Most of the things you ask about are SO OLD it will take some digging
through renames and moves.
Do you really need to know if "xfs_check" was added in 1994, or 1995, for
example? :)
This strikes me as a bit of an odd question; what is your motivation here?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-30 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 9:20 xfsprogs: minimum version with these commands Bogdan
2010-08-30 1:52 ` Eric Sandeen [this message]
2010-08-30 5:38 ` Michael Monnerie
2010-08-30 16:34 ` Bogdan
2010-08-30 16:44 ` Eric Sandeen
2010-09-01 15:59 ` Bogdan
2010-09-01 16:04 ` Eric Sandeen
2010-09-03 16:32 ` Bogdan
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=4C7B0EF6.5030505@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bogdandr@op.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.