From: Mike Frysinger <vapier@gentoo.org>
To: Kieran Bingham <kieran@bingham.xyz>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: including git commit in version
Date: Fri, 08 Jan 2016 19:07:00 -0000 [thread overview]
Message-ID: <20160108190657.GK25548@vapier.lan> (raw)
In-Reply-To: <CAB3z_Ro=T26HHhvse5jYL5U8F92a1FNsgkWYuesJApJuv-N2nA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On 08 Jan 2016 12:02, Kieran Bingham wrote:
> I'm currently carrying around a local patch on my development branches to
> add the SHA hash to the version.
> Would this be of use to propose to gdb-patches?
i had that in the back of my mind. i'd be ok with this sort of thing.
> It's much more useful to be able to tie into an explicit commit reference
> than just a date.
since the date is updated by a script, that can be tied to a commit in
a close range, so it's not that bad. it's not like the datestamp is
coming from `date` itself.
> Produces:
> > armv7-linux-gdb -v
> > GNU gdb (GDB) 7.10.1.20151205-git-gdb-7.10.1-release-2-g3e96ddbffb05
i think this is only when you're on a branch ? master doesn't
include all that. it is verbose, but i'm fine with it.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-01-08 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 1:02 git version has "-cvs" ? Mike Frysinger
2016-01-05 9:52 ` Joel Brobecker
2016-01-05 20:30 ` Mike Frysinger
2016-01-06 2:46 ` Joel Brobecker
[not found] ` <CAB3z_Ro=T26HHhvse5jYL5U8F92a1FNsgkWYuesJApJuv-N2nA@mail.gmail.com>
2016-01-08 19:07 ` Mike Frysinger [this message]
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=20160108190657.GK25548@vapier.lan \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=kieran@bingham.xyz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).