From: Leandro Facchinetti <me@leafac.com>
To: Ted Zlatanov <tzz@lifelogs.com>
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 06:39:03 -0400 [thread overview]
Message-ID: <87mw1jmhq0.fsf@leafac.com> (raw)
In-Reply-To: <87y4l39ws4.fsf@lifelogs.com>
> GM> git show emacs-24.4-1962-gccae04f
>
> GM> works fine for me.
>
> GM> (ccae04f205db7cffa0f247a463272f6c5af77122 if you prefer.)
>
> I've been using Git for years and didn't know this notation was built-in
> for `git show'. I kept trying `git show gccae04f' etc. and also looked
> through the `git log -p src/gnutls.c' history but didn't notice this
> commit. Thank you for explaining.
I learned something today!
From the `gitrevisions(7)' manual:
<describeOutput>, e.g. v1.7.4.2-679-g3bee7fb
Output from git describe; i.e. a closest tag, optionally followed by a dash and a number of commits, followed by a dash, a g, and an
abbreviated object name.
In fact:
$ git describe --tags ccae04f205db7cffa0f247a463272f6c5af77122
emacs-24.4-1962-gccae04f
And:
$ git show emacs-24.4-1962-gccae04f
Then shows the commit.
That's interesting!
I couldn't test the fix yet because I don't want to learn how to build
Emacs just now. Instead, I'll wait for the next release (lazy, I know).
I'll send the e-mail that closes the issue.
Thanks!
>
> GM> It's why I merged this report with #18208 5 days ago, thus closing it.
>
> Cool, thanks! I didn't see that in gmane.emacs.bugs and didn't think to check.
>
> GM> Presumably the desire was to indicate that the fixing commit came *after* 24.4.
>
> OK; understood. A commit ID would have been less confusing to me.
>
> Ted
--
Leandro Facchinetti <me@leafac.com>
https://www.leafac.com
GPG key: 3DF3D583
next prev parent reply other threads:[~2015-05-05 10:39 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 [this message]
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
[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=87mw1jmhq0.fsf@leafac.com \
--to=me@leafac.com \
--cc=20465@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=tzz@lifelogs.com \
/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).