author | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 14 Feb 2007 06:55:16 +0000 (01:55 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 14 Feb 2007 06:55:16 +0000 (01:55 -0500) | ||
commit | 26370f73c0e82bd67103e0868f84a44b536ff3fc | |
tree | 760faead94509017459054f34c4fc6f2ad2bf17c | tree | snapshot |
parent | ed3adde081645c5f93685b22d39f2d74e068873d | commit | diff |
git-gui: Prefer version file over git-describe.
Some distributions are using Git for part of their package
management system, but unpack Git's own source code for
delivery from the .tar.gz. This means that when we walk
up the directory tree with git-describe to locate a Git
repository, the repository we find is for the distribution
and *not* for git-gui. Consequently any tag we might find
there is bogus and does not apply to us.
In this case the version file should always exist and be
readable, as the packager is working from the released
.tar.gz sources. So we should always favor the version
file over anything git-describe guess for us.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Some distributions are using Git for part of their package
management system, but unpack Git's own source code for
delivery from the .tar.gz. This means that when we walk
up the directory tree with git-describe to locate a Git
repository, the repository we find is for the distribution
and *not* for git-gui. Consequently any tag we might find
there is bogus and does not apply to us.
In this case the version file should always exist and be
readable, as the packager is working from the released
.tar.gz sources. So we should always favor the version
file over anything git-describe guess for us.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
GIT-VERSION-GEN | diff | blob | history |