From: Jakub Narebski <jnareb@gmail.com>
To: Mathias Lafeldt <misfire@debugon.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/3] GIT-VERSION-GEN: make use of git describe --dirty
Date: Wed, 27 Oct 2010 07:28:53 -0700 (PDT) [thread overview]
Message-ID: <m3sjzriuc2.fsf@localhost.localdomain> (raw)
In-Reply-To: <4CC7D9CA.1080609@debugon.org>
Mathias Lafeldt <misfire@debugon.org> writes:
> Mathias Lafeldt wrote:
> > diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN
> > index d441d88..5c226f6 100755
> > --- a/GIT-VERSION-GEN
> > +++ b/GIT-VERSION-GEN
> > @@ -16,6 +16,10 @@ elif test -d .git -o -f .git &&
> > case "$VN" in
> > *$LF*) (exit 1) ;;
> > v[0-9]*)
> > + # As of Git v1.6.6, we can use "git describe --dirty" to
> > + # determine if the working tree is dirty. However, to still
> > + # have nice version numbers when building Git with older
> > + # versions of git installed, we keep using plumbing.
> > git update-index -q --refresh
> > test -z "$(git diff-index --name-only HEAD --)" ||
> > VN="$VN-dirty" ;;
> >
>
> Any feedback would be welcome.
I like it, also because people who use GIT-VERSION-GEN from git
repository as inspiration would get to know more modern technique.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-10-27 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1287746107.git.misfire@debugon.org>
2010-10-22 11:24 ` [PATCH 1/3] GIT-VERSION-GEN: make use of git describe --dirty Mathias Lafeldt
2010-10-22 15:11 ` Jonathan Nieder
2010-10-23 12:23 ` Mathias Lafeldt
2010-10-27 7:50 ` Mathias Lafeldt
2010-10-27 14:28 ` Jakub Narebski [this message]
2010-10-22 11:24 ` [PATCH 2/3] GIT-VERSION-GEN: tweak processing of version file Mathias Lafeldt
2010-10-22 11:24 ` [PATCH 3/3] GIT-VERSION-GEN: style nitpicks Mathias Lafeldt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3sjzriuc2.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=misfire@debugon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).