unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joseph Mingrone <jrm@ftfl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, kaushal.modi@gmail.com
Subject: Re: current-time and GMP
Date: Mon, 22 Oct 2018 16:38:46 -0300	[thread overview]
Message-ID: <86mur5ojp5.fsf@phe.ftfl.ca> (raw)
In-Reply-To: <8336sxuc1b.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 22 Oct 2018 20:27:44 +0300")

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Joseph Mingrone <jrm@ftfl.ca>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  Paul Eggert <eggert@cs.ucla.edu>,  Stefan Monnier <monnier@iro.umontreal.ca>,  Emacs developers <emacs-devel@gnu.org>
>> Date: Mon, 22 Oct 2018 13:24:04 -0300

>> >> > Please try again, I think I fixed this 2 days ago.
>> >> > Please try with the latest master branch.

>> >> Hah! I am on:

>> >> Emacs version: GNU Emacs 27.0.50 (build 28, x86_64-pc-linux-gnu, GTK+
>> >> Version 2.24.23)
>> >>  of 2018-10-19, built using commit fc3f93705543408b868feb7b93b8d77ab1c6ae53.

>> >> I see that this got fixed in
>> >> https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=efb214622a0f4e077c09e721d134552dfe76ef70.

>> >> Rebuilding now ..

>> > @Eli: I confirm the fix. Many thanks!

>> After building 969b561, I still see the message with `list-packages' under `emacs -Q'.

> Then yours is a different problem, and I'm afraid I cannot reproduce
> it here with the latest master.  Could it be that you have customized
> your packages or the repositories from which you produce the list of
> packages?  Or did something else that modifies the behavior of "emacs -Q"?

I don't think so.

--
Joseph

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2018-10-22 19:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  2:30 current-time and GMP Stefan Monnier
2018-08-29  9:07 ` Paul Eggert
2018-08-29 19:16   ` Stefan Monnier
2018-08-29 21:10     ` Helmut Eller
2018-10-02  1:09     ` Paul Eggert
2018-10-22 15:07       ` Joseph Mingrone
2018-10-22 15:15         ` Kaushal Modi
2018-10-22 15:49           ` Eli Zaretskii
2018-10-22 15:50         ` Eli Zaretskii
2018-10-22 15:57           ` Kaushal Modi
2018-10-22 16:10             ` Kaushal Modi
2018-10-22 16:24               ` Joseph Mingrone
2018-10-22 17:27                 ` Eli Zaretskii
2018-10-22 19:38                   ` Joseph Mingrone [this message]
2018-10-22 18:31         ` Paul Eggert
2018-10-22 19:39           ` Joseph Mingrone
2018-08-29 23:17 ` John Wiegley
2018-08-30  1:27   ` Stefan Monnier
2018-08-30  2:42     ` T.V Raman
2018-08-30  5:51       ` John Wiegley
2018-08-30  5:51     ` John Wiegley

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=86mur5ojp5.fsf@phe.ftfl.ca \
    --to=jrm@ftfl.ca \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).