From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Charles A. Roelli" <charles@aurox.ch>,
Keith David Bershatsky <esq@lawlist.com>,
27736@debbugs.gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#27736: OSX 10.6.8: Building from master branch fails.
Date: Wed, 28 Mar 2018 13:15:16 -0400 [thread overview]
Message-ID: <exo9j8f7ff.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <46d25462-4eb0-0bd0-f5ab-2b28bae98ee6@cs.ucla.edu> (Paul Eggert's message of "Tue, 27 Mar 2018 14:19:22 -0700")
Paul Eggert wrote:
> I noticed this problem when preparing a patch to catch this sort of
> issue. To fix this particular instance of the problem, I attempted to
> migrate the localtime workaround into editfns.c (so that the fix is
> more-general, and is not limited to org-clock), by installing the
> attached patches into master. Please give them a try, since I don't
> have easy access to Mac OS X. I'm still a bit fuzzy on exactly which
> timestamps cause Mac OS X localtime to go belly-up (is it timezone
> dependent?), so quite possibly the magic numbers in these patches need
> to be adjusted a bit so that the code will work in any timezone from
> TZ=AAA-24:59:59 to TZ=ZZZ24:59:59; please let me know.
The relevant org-clock.el code had been deleted in Org two months ago,
a change which was synced to Emacs today.
(Another example of my pet peeve, code in two repos being inefficient
for developers.)
next prev parent reply other threads:[~2018-03-28 17:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 15:18 bug#27736: OSX 10.6.8: Building from master branch fails Keith David Bershatsky
2017-07-17 15:29 ` Noam Postavsky
2017-07-17 16:10 ` Keith David Bershatsky
2017-07-17 16:38 ` Noam Postavsky
2017-07-17 18:05 ` Keith David Bershatsky
2017-07-17 18:48 ` Noam Postavsky
2017-07-17 19:43 ` Alan Third
2017-07-17 20:48 ` Charles A. Roelli
2017-07-17 21:37 ` Keith David Bershatsky
2017-07-18 5:08 ` Charles A. Roelli
2017-07-18 6:56 ` Keith David Bershatsky
2017-07-18 14:34 ` Eli Zaretskii
2017-07-18 16:07 ` Keith David Bershatsky
2017-07-18 18:42 ` Charles A. Roelli
2017-07-19 19:58 ` Charles A. Roelli
2017-07-19 22:48 ` Alan Third
2017-07-23 9:28 ` Charles A. Roelli
2017-07-24 15:50 ` Glenn Morris
2017-07-30 16:32 ` Charles A. Roelli
2017-11-05 18:03 ` Keith David Bershatsky
2017-11-05 18:15 ` Noam Postavsky
2017-11-05 20:01 ` Keith David Bershatsky
2017-11-06 2:20 ` Keith David Bershatsky
2017-11-06 19:41 ` Charles A. Roelli
2017-11-06 20:41 ` Charles A. Roelli
2017-11-07 2:13 ` Keith David Bershatsky
2017-11-07 20:20 ` Charles A. Roelli
2017-11-08 5:18 ` Keith David Bershatsky
2017-11-08 19:55 ` Charles A. Roelli
2018-03-27 21:19 ` Paul Eggert
2018-03-28 17:15 ` Glenn Morris [this message]
2018-03-28 19:02 ` Charles A. Roelli
2018-03-28 19:33 ` Paul Eggert
2018-03-28 22:08 ` Paul Eggert
2018-03-28 22:08 ` Paul Eggert
2018-03-28 18:54 ` Charles A. Roelli
2018-03-28 21:29 ` Paul Eggert
[not found] ` <805d95e1-bfc0-bb40-ced7-c10bb5a7256e@cs.ucla.edu>
2018-03-31 15:02 ` Charles A. Roelli
[not found] ` <m21sg02sr4.fsf@aurox.ch>
2018-04-01 20:32 ` Paul Eggert
[not found] <m2a800ve9b.wl%esq@lawlist.com>
2017-11-05 20:54 ` Charles A. Roelli
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=exo9j8f7ff.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=27736@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=eggert@cs.ucla.edu \
--cc=esq@lawlist.com \
--cc=npostavs@users.sourceforge.net \
/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.