* git hash for binutils 2.24 release
@ 2014-04-30 11:30 Andrew Bennett
2014-04-30 11:41 ` Andrew Bennett
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Bennett @ 2014-04-30 11:30 UTC (permalink / raw)
To: binutils
Hi,
I am trying to work out which git hash/commit was used to produce the binutils 2.24
release. The following commit appears to best match the files in the release tarball.
Would someone be able to confirm if I am correct?
Many thanks,
Andrew
commit 28edb9d05269b935d2648b331d294c2cf0522cd6
Author: Tristan Gingold <gingold@adacore.com>
Date: Mon Dec 2 10:48:01 2013 +0100
Bump version to 2.24
bfd/
2013-12-02 Tristan Gingold <gingold@adacore.com>
* configure.in: Bump version to 2.24
* Makefile.am (RELEASE): Set.
* configure, Makefile.in: Regenerate.
Andrew Bennett
Software Design Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: git hash for binutils 2.24 release
2014-04-30 11:30 git hash for binutils 2.24 release Andrew Bennett
@ 2014-04-30 11:41 ` Andrew Bennett
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Bennett @ 2014-04-30 11:41 UTC (permalink / raw)
To: binutils
> I am trying to work out which git hash/commit was used to produce the binutils 2.24
> release. The following commit appears to best match the files in the release tarball.
> Would someone be able to confirm if I am correct?
Just found the answer to my question by using git tag and git show binutils-2_24.
Sorry for the spam.
Regards,
Andrew
Andrew Bennett
Software Design Engineer, MIPS Processor IP
Imagination Technologies Limited
t: +44 (0)113 2429814
www.imgtec.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-04-30 11:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-04-30 11:30 git hash for binutils 2.24 release Andrew Bennett
2014-04-30 11:41 ` Andrew Bennett
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).