1--pretty[='<format>']:: 2 3 Pretty-prints the details of a commit. `--pretty` 4 without an explicit `=<format>` defaults to 'medium'. 5 If the commit is a merge, and if the pretty-format 6 is not 'oneline', 'email' or 'raw', an additional line is 7 inserted before the 'Author:' line. This line begins with 8 "Merge: " and the sha1s of ancestral commits are printed, 9 separated by spaces. Note that the listed commits may not 10 necessarily be the list of the *direct* parent commits if you 11 have limited your view of history: for example, if you are 12 only interested in changes related to a certain directory or 13 file. Here are some additional details for each format: 14 15 * 'oneline' 16 17 <sha1> <title line> 18+ 19This is designed to be as compact as possible. 20 21 * 'short' 22 23 commit <sha1> 24 Author: <author> 25 26 <title line> 27 28 * 'medium' 29 30 commit <sha1> 31 Author: <author> 32 Date: <date> 33 34 <title line> 35 36 <full commit message> 37 38 * 'full' 39 40 commit <sha1> 41 Author: <author> 42 Commit: <committer> 43 44 <title line> 45 46 <full commit message> 47 48 * 'fuller' 49 50 commit <sha1> 51 Author: <author> 52 AuthorDate: <date & time> 53 Commit: <committer> 54 CommitDate: <date & time> 55 56 <title line> 57 58 <full commit message> 59 60 61 * 'email' 62 63 From <sha1> <date> 64 From: <author> 65 Date: <date & time> 66 Subject: [PATCH] <title line> 67 68 full commit message> 69 70 71 * 'raw' 72+ 73The 'raw' format shows the entire commit exactly as 74stored in the commit object. Notably, the SHA1s are 75displayed in full, regardless of whether --abbrev or 76--no-abbrev are used, and 'parents' information show the 77true parent commits, without taking grafts nor history 78simplification into account.