git log –all

Despite git’s power, it can be very un-intuitive.

E.g. you run git log expecting to see all log messages. Not true. You have to run git log –all to see all of them (* see Note 1 below).

And the output is not obvious. e.g.

commit c751111
Merge: fc07fdf 4059fc6
Author: <author>
Date:   Mon Apr 20 14:42:08 2015 -0400

WIP on dev/app/admin/categories: fc07fdf with auto categories

commit 4059fc6
Author: <author>
Date:   Mon Apr 20 14:42:08 2015 -0400

index on dev/app/admin/categories: fc07fdf with auto categories

commit fc07fdf
Author: <author>
Date:   Mon Apr 20 14:39:01 2015 -0400

with auto categories

Let’s go through each line:

1: shows the SHA-1 reference of that commit

2: it seems to have been a merge between 2 other commits

3: author details

4: date

5: this is an auto-generated stash message. <WIP => work in progress> on <name of branch>: <commit SHA-1 reference> <commit message>

The next line of interest is

index on dev/app/admin

Presumably this was auto-generated by git. I don’t have a clue there.

 

Note 1: another example of the unintuitiveness of git. It turns out that git log –all does NOT show all the log messages. Here’s what it actually does:

http://stackoverflow.com/questions/29756637/what-does-git-log-all-do

Leave a Reply

Your email address will not be published. Required fields are marked *