| commit | c3e3cd4bf8c94cc2f4fa8d8f7751553037e06004 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sat, 13 Jan 2007 22:28:16 +0000 (13 17:28 -0500) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Mon, 15 Jan 2007 05:17:27 +0000 (14 21:17 -0800) | ||
| tree | 662c630e258a44ad1649048847f4b41f23b0141f | treesnapshot (tar.gz zip) |
| parent | dccd0c2abdb958daf6f168ba925b67441dc6be61 | commitdiff |
Hash tags by commit SHA1 in git-describe.
If a project has a very large number of tags then git-describe
will spend a good part of its time looping over the tags testing
them one at a time to determine if it matches a given commit.
For 10 tags this is not a big deal, but for hundreds of tags the
time could become considerable if we don't find an exact match for
the input commit and we need to walk back along the history chain.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
If a project has a very large number of tags then git-describe
will spend a good part of its time looping over the tags testing
them one at a time to determine if it matches a given commit.
For 10 tags this is not a big deal, but for hundreds of tags the
time could become considerable if we don't find an exact match for
the input commit and we need to walk back along the history chain.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| builtin-describe.c | diffblobblamehistory |