@@ -129,11 +129,13 @@ $ git who -- foo
129129```
130130
131131#### Options
132- The ` -m ` , ` -l ` , and ` -f ` flags allow you to sort the table by different
132+ The ` -m ` , ` -c ` , ` - l` , and ` -f ` flags allow you to sort the table by different
133133metrics.
134134
135135The ` -m ` flag sorts the table by the "Last Edit" column, showing who
136- edited the repository most recently.
136+ edited the repository most recently. The ` -c ` flag sorts the table by first
137+ edit, so that the authors who committed to the repository earliest are at the
138+ top.
137139
138140The ` -l ` flag sorts the table by number of lines modified, adding some more
139141columns:
@@ -266,13 +268,11 @@ Parser/.........................Guido van Rossum (182)
266268of this README._ )
267269
268270Note that, whether or not the ` -a ` flag is used, commits that
269- edited files
270- not in the working tree will still count toward the total displayed
271- next to ancestor directories of that file. In the above two examples,
272- Guido van Rossum is shown as the overall highest committer to the
273- ` Parser/ ` directory, though it takes listing the entire
274- tree with the ` -a ` flag to see that most of his commits were to
275- files that have since been moved or deleted.
271+ edited files not in the working tree will still count toward the total
272+ displayed next to ancestor directories of that file. In the above two examples,
273+ Guido van Rossum is shown as the overall highest committer to the ` Parser/ `
274+ directory, though it takes listing the entire tree with the ` -a ` flag to see
275+ that most of his commits were to files that have since been moved or deleted.
276276
277277Like with the ` table ` subcommand, you can specify a "commit-ish". This
278278next example shows changes to the ` Parser/ ` directory that happened
@@ -298,7 +298,9 @@ changes introduced by a branch.
298298
299299#### Options
300300The ` tree ` subcommand, like the ` table ` subcommand, supports the ` -l ` , ` -f ` ,
301- and ` -m ` flags. The ` -l ` flag will annotate each file tree node with the
301+ ` -m ` , and ` -c ` flags.
302+
303+ The ` -l ` flag will annotate each file tree node with the
302304author who has added or removed the most lines at that path:
303305
304306```
@@ -334,8 +336,9 @@ Parser/.........................Pablo Galindo (72,917 / 47,102)
334336└── token.c.....................Serhiy Storchaka (233 / 0)
335337```
336338
337- The ` -f ` flag will pick authors based on files touched and the ` -m ` flag will
338- pick an author based on last modification time.
339+ The ` -f ` flag will pick authors based on number of files edited. The ` -m ` flag
340+ will pick an author based on last modification time while the ` -c ` flag picks
341+ the author who first edited a file.
339342
340343You can limit the depth of the tree printed by using the ` -d ` flag. The depth
341344is measured from the current working directory.
@@ -345,8 +348,8 @@ The `-a` flag has already been mentioned.
345348Run ` git who tree --help ` to see all options available for the ` tree ` subcommand.
346349
347350### The ` hist ` Subcommand
348- The ` hist ` subcommand prints out a little bar chart / timeline of commit activity
349- showing the history of contributions to the repository.
351+ The ` hist ` subcommand prints out a little bar chart / timeline of commit
352+ activity showing the history of contributions to the repository.
350353
351354```
352355~/clones/cpython$ git who hist
@@ -445,7 +448,8 @@ Jan 2025 ┤ ##--------- Bénédikt Tran (26)
445448```
446449
447450#### Options
448- The ` hist ` subcommand supports the ` -l ` and ` -f ` flags but not the ` -m ` flag:
451+ The ` hist ` subcommand supports the ` -l ` and ` -f ` flags but not the ` -m ` or ` -c `
452+ flags:
449453
450454```
451455~/repos/cpython$ git who hist -l iOS/
0 commit comments