[PATCH] git-project-version

Subsystems: kernel build + files below scripts/ (unless maintained elsewhere), the rest

STALE3736d

3 messages, 2 authors, 2016-06-15 · open the first message on its own page

[PATCH] git-project-version

From: Santi Béjar <hidden>
Date: 2016-06-15 22:42:35

Introduce an easy way for projects to get its git version. This is
something that other projects using git would like to do, and we don't
want them all reinventing the wheel.

Signed-off-by: Santi Béjar <redacted>
---
Hi *,

I would prefer an output with an explicit git string as:

v1.4.2-rc3-git46faaaf

Also I would prefer the dirty state with an ending M as in:

v1.4.2-rc3-git46faaaf-M

to use the same letter of the diff family.

   Santi

 Makefile               |    3 ++-
 git-project-version.sh |    9 +++++++++
 2 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/Makefile b/Makefile
index d662bd6..7c4e360 100644
--- a/Makefile
+++ b/Makefile
@@ -169,7 +169,8 @@ SCRIPT_SH = \
 	git-applymbox.sh git-applypatch.sh git-am.sh \
 	git-merge.sh git-merge-stupid.sh git-merge-octopus.sh \
 	git-merge-resolve.sh git-merge-ours.sh \
-	git-lost-found.sh git-quiltimport.sh
+	git-lost-found.sh git-quiltimport.sh \
+	git-project-version.sh
 
 SCRIPT_PERL = \
 	git-archimport.perl git-cvsimport.perl git-relink.perl \
diff --git a/git-project-version.sh b/git-project-version.sh
new file mode 100755
index 0000000..88b21fa
--- /dev/null
+++ b/git-project-version.sh
@@ -0,0 +1,9 @@
+#!/bin/sh
+# First try git-describe.
+VN=$(git describe --abbrev=4 HEAD 2>/dev/null) ||
+VN=$(git rev-parse --short HEAD | sed -e 's/^/g/')
+
+dirty=$(sh -c 'git diff-index --name-only HEAD' 2>/dev/null) || dirty=
+[ "$dirty" ] && VN="$VN-dirty"
+
+echo $VN
-- 
1.4.2.rc3.g3f0a-dirty

Re: [PATCH] git-project-version

From: Petr Baudis <hidden>
Date: 2016-06-15 22:42:41

Dear diary, on Fri, Aug 04, 2006 at 11:48:25PM CEST, I got a letter
where Santi Béjar [off-list ref] said that...
Introduce an easy way for projects to get its git version. This is
something that other projects using git would like to do, and we don't
want them all reinventing the wheel.

Signed-off-by: Santi Béjar <redacted>
Perhaps it would be more useful to have a flag for git-describe to
describe not the (HEAD) commit but your working copy (thus HEAD + check
for the dirtyness).

-- 
				Petr "Pasky the Hater of Too Many
					Commands" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

Re: [PATCH] git-project-version

From: Santi <hidden>
Date: 2016-06-15 22:42:41

2006/9/24, Petr Baudis [off-list ref]:
Dear diary, on Fri, Aug 04, 2006 at 11:48:25PM CEST, I got a letter
where Santi Béjar [off-list ref] said that...
quoted
Introduce an easy way for projects to get its git version. This is
something that other projects using git would like to do, and we don't
want them all reinventing the wheel.

Signed-off-by: Santi Béjar <redacted>
Perhaps it would be more useful to have a flag for git-describe to
describe not the (HEAD) commit but your working copy (thus HEAD + check
for the dirtyness).
Sure.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help