aboutsummaryrefslogtreecommitdiff
path: root/show-branch.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@osdl.org>2005-10-21 16:40:54 -0700
committerJunio C Hamano <junkio@cox.net>2005-10-22 22:49:52 -0700
commit1b9e059d3503f935bb3eebb073cfb0f0401e2adf (patch)
treeb5543a40894235a62424dcce9acbbacdfc63c26e /show-branch.c
parentcf4845441c3931731643859dc80a79e52bcd3e0f (diff)
downloadgit-1b9e059d3503f935bb3eebb073cfb0f0401e2adf.tar.gz
git-1b9e059d3503f935bb3eebb073cfb0f0401e2adf.tar.xz
git-rev-list: add "--dense" flag
This is what the recent git-rev-list changes have all been gearing up for. When we use a path filter to git-rev-list, the new "--dense" flag asks git-rev-list to compress the history so that it _only_ contains commits that change files in the path filter. It also rewrites the parent information so that tools like "gitk" will see the result as a dense history tree. For example, on the current kernel archive: [torvalds@g5 linux]$ git-rev-list HEAD | wc -l 9904 [torvalds@g5 linux]$ git-rev-list HEAD -- kernel | wc -l 5442 [torvalds@g5 linux]$ git-rev-list --dense HEAD -- kernel | wc -l 356 which shows that while we have almost ten thousand commits, we can prune down the work to slightly more than half by only following the merges that are interesting. But further, we can then compress the history to just 356 entries that actually make changes to the kernel subdirectory. To see this in action, try something like gitk --dense -- gitk to see just the history that affects gitk. Or, to show that true parallel development still remains parallel, do gitk --dense -- daemon.c which shows some parallel commits in the current git tree. Signed-off-by: Linus Torvalds <torvalds@osdl.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'show-branch.c')
0 files changed, 0 insertions, 0 deletions