From: Ted Zlatanov <tzz@lifelogs.com>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Leandro Facchinetti <me@leafac.com>,
20465@debbugs.gnu.org
Subject: bug#20465: 24.4; GnuTLS integration seems faulty
Date: Tue, 05 May 2015 10:28:45 -0400 [thread overview]
Message-ID: <877fsn9jz6.fsf@lifelogs.com> (raw)
In-Reply-To: <87383b5cv5.fsf@yahoo.fr> (Nicolas Richard's message of "Tue, 05 May 2015 16:15:58 +0200")
On Tue, 05 May 2015 16:15:58 +0200 Nicolas Richard <theonewiththeevillook@yahoo.fr> wrote:
NR> Fwiw, emacs-24.4-1962-gccae04f is the kind of output given by
NR> "git describe --tags". The constituents are:
NR> - emacs-24.4 : a tag name
NR> - 1962 : IIRC this is the number of commits since the tag
NR> - g : I don't know why this letter is here. I guess its sole purpose is to
NR> *not* be a hex digit.
NR> - ccae04f : first few digits of the commit hash.
Aha, that `g' is what threw me. I didn't notice it was not a hex
digit--`git show ccae04f' works perfectly when you omit the `g'. Thanks
to everyone for the patient explanations.
Thanks
Ted
next prev parent reply other threads:[~2015-05-05 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 19:34 bug#20465: 24.4; GnuTLS integration seems faulty Leandro Facchinetti
2015-04-29 20:36 ` Andreas Schwab
2015-04-29 20:54 ` Leandro Facchinetti
2015-05-04 22:08 ` Ted Zlatanov
2015-05-05 0:43 ` Leandro Facchinetti
2015-05-05 0:52 ` Glenn Morris
2015-05-05 9:52 ` Ted Zlatanov
2015-05-05 10:39 ` Leandro Facchinetti
2015-05-05 10:50 ` Andreas Schwab
2015-04-29 20:48 ` Andreas Schwab
2015-05-04 22:08 ` Ted Zlatanov
2015-05-04 22:25 ` Andreas Schwab
2015-05-04 22:38 ` Ted Zlatanov
2015-05-05 0:40 ` Leandro Facchinetti
2015-05-05 14:15 ` Nicolas Richard
2015-05-05 14:28 ` Ted Zlatanov [this message]
[not found] ` <handler.20465.B.14303394254904.ack@debbugs.gnu.org>
2015-05-05 10:41 ` bug#20465: Acknowledgement (24.4; GnuTLS integration seems faulty) Leandro Facchinetti
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fsn9jz6.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=20465@debbugs.gnu.org \
--cc=me@leafac.com \
--cc=schwab@linux-m68k.org \
--cc=theonewiththeevillook@yahoo.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).