---
 docs/yum.8 |   18 +++++++++++++-----
 1 files changed, 13 insertions(+), 5 deletions(-)

diff --git a/docs/yum.8 b/docs/yum.8
index a1375de..255c755 100644
--- a/docs/yum.8
+++ b/docs/yum.8
@@ -69,7 +69,7 @@ gnome\-packagekit application\&.
 .br
 .I \fR * version [ all | installed | available | group-* | nogroups* | 
grouplist | groupinfo ]
 .br
-.I \fR * history 
[info|list|packages-list|summary|addon-info|redo|undo|rollback|new] 
+.I \fR * history 
[info|list|packages-list|packages-info|summary|addon-info|redo|undo|rollback|new|sync|stats]
 
 .br
 .I \fR * load-transaction [txfile]
 .br
@@ -323,15 +323,17 @@ and so takes sub-commands:
 .IP "\fBhistory\fP"
 The history command allows the user to view what has happened in past
 transactions (assuming the history_record config. option is set). You can use
-info/list/packages-list/summary to view what happened, undo/redo/rollback to 
act
-on that information and new to start a new history file.
+info/list/packages-list/packages-info/summary to view what happened,
+undo/redo/rollback to act on that information and new to start a new history
+file.
 
 The info/list/summary commands take either a transaction id or a package (with
 wildcards, as in \fBSpecifying package names\fP), all three can also be passed
 no arguments. list can be passed the keyword "all" to list all the 
transactions.
 
-The packages-list command takes a package  (with wildcards, as in
-\fBSpecifying package names\fP).
+The packages-list/packages-info commands takes a package  (with wildcards, as 
in
+\fBSpecifying package names\fP). And show data from the point of view of that
+package.
 
 The undo/redo/rollback commands take either a single transaction id or the
 keyword last and an offset from the last transaction (Eg. if you've done 250
@@ -351,6 +353,12 @@ transactions 1 and 4.
 The addon-info command takes a transaction ID, and the packages-list command
 takes a package (with wildcards).
 
+The stats command shows some statistics about the current history DB.
+
+The sync commands allows you to change the rpmdb/yumdb data stored for any
+installed packages, to whaever is in the current rpmdb/yumdb (this is mostly
+useful when this data was not stored when the package went into the history 
DB).
+
 In "history list" you can change the behaviour of the 2nd column via. the
 configuration option history_list_view.
 
-- 
1.7.6

_______________________________________________
Yum-devel mailing list
[email protected]
http://lists.baseurl.org/mailman/listinfo/yum-devel

Reply via email to