Matthieu Moy <matthieu....@grenoble-inp.fr> writes: > I'd say either this, or add the missing features to "git log" to make my > suggestion possible (after all, if some people like "git whatchanged", > then maybe the feature would be of interest to "git log" users ?).
There is no _missing feature_ per se. whatchanged by default (1) gives diffs, (2) does not show empty commits, and (3) uses raw format for its diff output. I am fuzzy about where the name of the command and its default behaviour came from (I suspect it may have been modelled after another SCM kernel folks were familiar with), but I do not mind if somebody does an archaeology (read: ask Linus) and reduce the document to something like this: git-whatchanged(1) ================== NAME ---- git-whatchanged - Show logs with difference each commit introduces SYNOPSIS -------- [verse] 'git whatchanged' <option>... DESCRIPTION ----------- Shows commit logs and diff output each commit introduces. This is essentially the same as linkgit:git-log run with different defaults. The command name and behaviour were originally borrowed from XXXX and the command is kept primarily for historical reasons (fingers of many people who learned Git by reading Linux kernel mailing list are trained to type it before `git log` was invented). New users are encouraged to use linkgit:git-log instead. Examples -------- `git whatchanged -p v2.6.12.. include/scsi drivers/scsi`:: Show as patches the commits since version 'v2.6.12' that changed any file in the include/scsi or drivers/scsi subdirectories `git whatchanged --since="2 weeks ago" -- gitk`:: Show the changes during the last two weeks to the file 'gitk'. The "--" is necessary to avoid confusion with the *branch* named 'gitk' GIT --- Part of the linkgit:git suite -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html