On 09/17/2010 04:24 PM, Piotr Drąg wrote:
Anyway, reverting a bad commit is easy, basically it's "git
commit_hash". Commit hash can be obtained from some git command I
don't know or from my favorite gitweb. :)
(in case it's useful, or anyone's curious)
The command "git log" could be what you want. It shows the history
of what has been committed, with the most recent first, then the commit
before it, then the one before that, and so on:
$ git log
Author: Eric Blake <eblake(a)redhat.com>
Date: Thu Sep 9 20:32:50 2010 -0600
tests: clean up qemuargv2xmltest
Since commit 107a7bd06bc, the extraFlags argument was unused.
* tests/qemuargv2xmltest.c (DO_TEST): Drop extraFlags argument.
Adjust all callers.
Author: Justin Clift <jclift(a)redhat.com>
Date: Thu Sep 16 22:14:18 2010 +1000
docs: reworked the policykit patch submitted by Patrick Dignan
Tweaked the PolicyKit documentation improvement patch submitted
by Patrick Dignan.
Additionally, removed the reference to PolicyKit.conf, which is
no longer used by PolicyKit, plus added a link to the expanded
PolicyKit example page on the wiki.
There's also a "--oneline" version:
$ git log --oneline
10c5928 tests: clean up qemuargv2xmltest
df1718c docs: reworked the policykit patch submitted by Patrick Dignan
5bc4307 docs: fix the xml validity errors regarding name and id
8ae354f build: avoid non-portable IPv6 struct member, for MacOS X
58ba49a virsh: change wexitstatus order to allow compilation on mac osx
63d1b07 libvirtd: improve the error message displayed on tls client
8a93daf maint: silence warning from libtool
38ba6e1 Rebuild network filter for UML guests on updates
I'm not a git expert, it's just something I'm learning from necessity. :)
Regards and best wishes,