"Baumann, Moritz" <moritz.baumann@xxxxxxx> writes: > Is there any alternative for my use case that doesn't involve walking the > commits one-by-one? I do not think there currently is such an option, and not showing the same object twice is pretty much fundamental in the operation of the command, so it is unclear what the new feature should look like. Should it also show the same commit it encounters during its history walk (remember, a history can have forks and merges in it) in duplicates if it encounters it more than once? Should it show all the subtrees and blobs in the tree of each commit, even if most of them do not change from commit to commit? How does the user control which ones are duplicated and which ones are to be visited only once? How does the command line option used by the user to tell the command to give such a choice look like? Once there things are designed well, implementation of such a mode would not be too hard. By the way, "rev-list" internally uses walking the commits one-by-one, anyway ;-).
