summaryrefslogtreecommitdiffstats
path: root/man1/git-describe.1
diff options
context:
space:
mode:
Diffstat (limited to 'man1/git-describe.1')
-rw-r--r--man1/git-describe.110
1 files changed, 5 insertions, 5 deletions
diff --git a/man1/git-describe.1 b/man1/git-describe.1
index 728928bec..da74b212e 100644
--- a/man1/git-describe.1
+++ b/man1/git-describe.1
@@ -2,12 +2,12 @@
.\" Title: git-describe
.\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\" Date: 2023-06-13
+.\" Date: 2023-06-23
.\" Manual: Git Manual
-.\" Source: Git 2.41.0.28.gd7d8841f67
+.\" Source: Git 2.41.0.191.g6ff334181c
.\" Language: English
.\"
-.TH "GIT\-DESCRIBE" "1" "2023\-06\-13" "Git 2\&.41\&.0\&.28\&.gd7d8841" "Git Manual"
+.TH "GIT\-DESCRIBE" "1" "2023\-06\-23" "Git 2\&.41\&.0\&.191\&.g6ff334" "Git Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -146,7 +146,7 @@ v1\&.0\&.4\-14\-g2414721
.sp
i\&.e\&. the current head of my "parent" branch is based on v1\&.0\&.4, but since it has a few commits on top of that, describe has added the number of additional commits ("14") and an abbreviated object name for the commit itself ("2414721") at the end\&.
.sp
-The number of additional commits is the number of commits which would be displayed by "git log v1\&.0\&.4\&.\&.parent"\&. The hash suffix is "\-g" + an unambigous abbreviation for the tip commit of parent (which was \fB2414721b194453f058079d897d13c4e377f92dc6\fR)\&. The length of the abbreviation scales as the repository grows, using the approximate number of objects in the repository and a bit of math around the birthday paradox, and defaults to a minimum of 7\&. The "g" prefix stands for "git" and is used to allow describing the version of a software depending on the SCM the software is managed with\&. This is useful in an environment where people may use different SCMs\&.
+The number of additional commits is the number of commits which would be displayed by "git log v1\&.0\&.4\&.\&.parent"\&. The hash suffix is "\-g" + an unambiguous abbreviation for the tip commit of parent (which was \fB2414721b194453f058079d897d13c4e377f92dc6\fR)\&. The length of the abbreviation scales as the repository grows, using the approximate number of objects in the repository and a bit of math around the birthday paradox, and defaults to a minimum of 7\&. The "g" prefix stands for "git" and is used to allow describing the version of a software depending on the SCM the software is managed with\&. This is useful in an environment where people may use different SCMs\&.
.sp
Doing a \fIgit describe\fR on a tag\-name will just show the tag name:
.sp
@@ -208,7 +208,7 @@ If an exact match was not found, \fIgit describe\fR will walk back through the c
If multiple tags were found during the walk then the tag which has the fewest commits different from the input commit\-ish will be selected and output\&. Here fewest commits different is defined as the number of commits which would be shown by \fBgit log tag\&.\&.input\fR will be the smallest number of commits possible\&.
.SH "BUGS"
.sp
-Tree objects as well as tag objects not pointing at commits, cannot be described\&. When describing blobs, the lightweight tags pointing at blobs are ignored, but the blob is still described as <committ\-ish>:<path> despite the lightweight tag being favorable\&.
+Tree objects as well as tag objects not pointing at commits, cannot be described\&. When describing blobs, the lightweight tags pointing at blobs are ignored, but the blob is still described as <commit\-ish>:<path> despite the lightweight tag being favorable\&.
.SH "GIT"
.sp
Part of the \fBgit\fR(1) suite