| commit | d68dc34cb41c30515e64766c303c2930994e5085 | |
| author | Björn Steinbrink <B.Steinbrink@gmx.de> | |
| Thu, 6 Aug 2009 12:15:14 +0000 (6 14:15 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 6 Aug 2009 20:35:55 +0000 (6 13:35 -0700) | ||
| tree | 40f8f5c937a55242dd9c45a7f1296e521beb6dc3 | treesnapshot (tar.gz zip) |
| parent | 4cfbe06fc788aad7bb4e5ea0c2c93345840acc28 | commitdiff |
git-describe: Die early if there are no possible descriptions
If we find no refs that may be used for git-describe with the current
options, then die early instead of pointlessly walking the whole
history.
In git.git with all the tags dropped, this makes "git describe" go down
from 0.244 to 0.003 seconds for me. This is especially noticeable with
"git submodule status" which calls describe with increasing levels of
allowed refs to be matched. For a submodule without tags, this means
that it walks the whole history in the submodule twice (first annotated,
then plain tags), just to find out that it can't describe the commit
anyway.
Signed-off-by: Björn Steinbrink <B.Steinbrink@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
If we find no refs that may be used for git-describe with the current
options, then die early instead of pointlessly walking the whole
history.
In git.git with all the tags dropped, this makes "git describe" go down
from 0.244 to 0.003 seconds for me. This is especially noticeable with
"git submodule status" which calls describe with increasing levels of
allowed refs to be matched. For a submodule without tags, this means
that it walks the whole history in the submodule twice (first annotated,
then plain tags), just to find out that it can't describe the commit
anyway.
Signed-off-by: Björn Steinbrink <B.Steinbrink@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin-describe.c | diffblobblamehistory |