From fbfae11d602e56780a02f51770a881b9287f081d Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Thu, 22 Aug 2013 18:03:42 +0200 Subject: examine the log MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- using-git.texinfo | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/using-git.texinfo b/using-git.texinfo index 546aecc..2498fa6 100644 --- a/using-git.texinfo +++ b/using-git.texinfo @@ -1127,6 +1127,7 @@ bisection. @menu * Tagging versions:: * Cherry picking:: +* Examine the log:: @end menu @@ -1185,6 +1186,24 @@ git cherry-pick COMMIT_ID +@node Examine the log +@section Examine the log + +So how are you going to cherry-pick commits +if you do not know their commit ID:s? Simple, +you use Git's log tool to find their ID:s. + +The log will only show earlier commits in +the branch then the currently checked out +commit. Typing @command{git log} will show +you the commit's ID, author, date, and +commit message. You can limit the commits +to a commits where specify files has been +changed by appending those files to the +command. + + + @node Glossary @appendix Glossary -- cgit v1.2.3-70-g09d2