If some of the changes modify the same file, try to use git add -patch to partially stage files (covered in detail in Interactive Staging). If you can, try to make your changes digestible – don’t code for a whole weekend on five different issues and then submit them all as one massive commit on Monday.Įven if you don’t commit during the weekend, use the staging area on Monday to split your work into at least one commit per issue, with a useful message per commit. Next, try to make each commit a logically separate changeset. Options include oneline, short, full, fuller, and format (where you specify your own format). Show only the first few characters of the SHA-1 checksum instead of all 40.ĭisplay the date in a relative format (for example, “2 weeks ago”) instead of using the full date format.ĭisplay an ASCII graph of the branch and merge history beside the log output. Show the list of files affected with added/modified/deleted information as well. Show the list of files modified after the commit information. Show statistics for files modified in each commit.ĭisplay only the changed/insertions/deletions line from the -stat command.
P4merge rest truncated Patch#
Show the patch introduced with each commit.
Those are only some simple output-formatting options to git log – there are many more.Ĭommon options to git log lists the options we’ve covered so far, as well as some other common formatting options that may be useful, along with how they change the output of the log command.
0 kommentar(er)
