The commit 52f425e1 (August, 30th 2013) mentions: Encourage new users to use ‘log‘ instead. These days, these commands are unified and just have different defaults. ‘git log‘ only allowed you to view the log messages and no diffs when it was added in early June 2005. It was only in early April 2006 that the … Read more
git version 1.8.4 added an –author-date-order argument to git log; according to the release notes, “the output is topologically sorted and commits in parallel histories are shown intermixed together based on the author timestamp.”
If you want to find all commits where the commit message contains a given word, use $ git log –grep=word If you want to find all commits where “word” was added or removed in the file contents (to be more exact: where the number of occurrences of “word” changed), i.e., search the commit contents, use … Read more
TLDR; as mentioned in GitMerge 2019: git config –global core.commitGraph true git config –global gc.writeCommitGraph true cd /path/to/repo git commit-graph write Actually (see at the end), the first two config are not needed with Git 2.24+ (Q3 2019): they are true by default. As T4cC0re mentions in the comments: If you are on git version … Read more
git log –oneline –pretty=”@%h” –stat |grep -v \| | tr “\n” ” ” | tr “@” “\n” This will show something like this: a596f1e 1 file changed, 6 insertions(+), 3 deletions(-) 4a9a4a1 1 file changed, 6 deletions(-) b8325fd 1 file changed, 65 insertions(+), 4 deletions(-) 968ef81 1 file changed, 4 insertions(+), 5 deletions(-)
git log has option –first-parent, so you won’t get topic history. When merged from master, the master commits are the first parents in merge. Git log allows to display only those commits with –first-parent, so you get the right stuff.
As of git 1.8.3 (May 24, 2013), you can use %C(auto) to decorate %d in the format string of git log. From the release notes: * “git log –format” specifier learned %C(auto) token that tells Git to use color when interpolating %d (decoration), %h (short commit object name), etc. for terminal output.)
In case it helps someone else who lands here like I did, after a bit of researching I found out that using ISO8601 format also works: git log –since=”2014-02-12T16:36:00-07:00″ This will give you precision down to the second. Note: you can also use: git log –after=”2014-02-12T16:36:00-07:00″ git log –before=”2014-02-12T16:36:00-07:00″ git log –since=”1 month ago” git … Read more
Assuming that your branch was created off of master, then while in the branch (that is, you have the branch checked out): git cherry -v master or git log master.. If you are not in the branch, then you can add the branch name to the “git log” command, like this: git log master..branchname If … Read more
You’re in the less program, which makes the output of git log scrollable. Type q to exit this screen. Type h to get help. If you don’t want to read the output in a pager and want it to be just printed to the terminal define the environment variable GIT_PAGER to cat or set core.pager … Read more