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: Mon, 04 May 2015 20:40:42 -0400 [thread overview]
Message-ID: <87pp6fn9f9.fsf@leafac.com> (raw)
In-Reply-To: <87y4l455od.fsf@lifelogs.com>
> I am either unable to copy and paste or unable to pull some revisions or
> otherwise blind, because I can't find that commit ID. Sorry to be a pest
> but could you give the full hash, as `git log' would show it?
To be honest, I thought that was the commit hash and tried to look for
it, to satisfy my curiosity. I couldn't find it either, but I figured it
was just me being dumb.
At least, I can point this related issue (it was listed on the bug
tracker along with the issue I opened):
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18208
--
Leandro Facchinetti <me@leafac.com>
https://www.leafac.com
GPG key: 3DF3D583
next prev parent reply other threads:[~2015-05-05 0:40 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pp6fn9f9.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.