https://github.com/git/git
Revision 5f0883381054b796b643dcff974435633eed8a79 authored by elliottcable on 01 June 2013, 04:53:19 UTC, committed by elliottcable on 04 June 2013, 15:23:43 UTC
--date-order is an excellent alternative to --topo-order if you want a feel for
the *actual history*, chronologically, of your project. I use it often, with
--graph as well; it's a great way to get an overview of a project's recent
development history.

However, in a project that rebases various in-development topic-branches often,
it gets hard to demonstrate a *chronological history* of changes to the
codebase, as this always “resets” the COMMITTER_DATE (which --date-order uses)
to the time the rebase happened; which often means ‘last time all of the
topic-branches were rebased on the latest fixes in master.’

Thus, I've added an --authorship-order version of --date-order, which relies
upon the AUTHOR_DATE instead of the COMMITTER_DATE; this means that old commits
will continue to show up chronologically in-order despite rebasing.
1 parent b5c2675
Raw File
Tip revision: 5f0883381054b796b643dcff974435633eed8a79 authored by elliottcable on 01 June 2013, 04:53:19 UTC
rev-list: add --authorship-order alternative ordering
Tip revision: 5f08833
progress.h
#ifndef PROGRESS_H
#define PROGRESS_H

struct progress;

void display_throughput(struct progress *progress, off_t total);
int display_progress(struct progress *progress, unsigned n);
struct progress *start_progress(const char *title, unsigned total);
struct progress *start_progress_delay(const char *title, unsigned total,
				       unsigned percent_treshold, unsigned delay);
void stop_progress(struct progress **progress);
void stop_progress_msg(struct progress **progress, const char *msg);

#endif
back to top