unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnulib@gnu.org, emacs-devel@gnu.org
Subject: Re: syncing Emacs from sources maintained elsewhere
Date: Thu, 27 Jan 2011 01:22:42 -0800	[thread overview]
Message-ID: <4D413962.4060603@cs.ucla.edu> (raw)
In-Reply-To: <838vy7y8jz.fsf@gnu.org>

On 01/26/2011 07:43 AM, Eli Zaretskii wrote:

>   . Is it true that time_r.c is needed only by mktime.c?

Yes, for now, but once I add the strftime module, time_r.c will also be needed
by strftime.c, and in that case MinGW will definitely need to worry about
time_r.c.

strftime is quite likely to be added.  I've already coded it up and tested
it, and it works fine on POSIXy platforms.  I plan to add it to Emacs
soon.  Once it's in, Emacs's format-time-string function can start supporting
higher-resolution time stamps.

>   . Is it true that stddef.in.h, unistd.in.h, and time.in.h are needed
>     only on systems which have "issues" with the corresponding
>     standard headers?

The "issues" are either with the headers, or with the implementations of
functions declared by the headers.

>     is it okay to compile gnulib sources in
>     lib/ without editing these 3 into the corresponding *.h files?

If the MinGW headers and implementations are good enough, you should
be OK without the .h files.  I'd be surprised if that were true, though.



  reply	other threads:[~2011-01-27  9:22 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  0:50 syncing Emacs from sources maintained elsewhere Paul Eggert
2011-01-11  1:38 ` Miles Bader
2011-01-11  4:39   ` Paul Eggert
2011-01-17 20:37 ` Paul Eggert
2011-01-17 21:35   ` Stefan Monnier
2011-01-17 22:12     ` Paul Eggert
2011-01-18 10:11   ` Andy Moreton
2011-01-18 15:20     ` Eli Zaretskii
2011-01-18 18:13       ` Paul Eggert
2011-01-18 22:57         ` Eli Zaretskii
2011-01-19  0:36           ` Paul Eggert
2011-01-19 15:03             ` Eli Zaretskii
2011-01-19  1:20         ` Glenn Morris
2011-01-19  6:04           ` Paul Eggert
     [not found]             ` <4D368D16.7020702@swipnet.se>
2011-01-19  9:00               ` Glenn Morris
2011-01-19 10:38                 ` Paul Eggert
2011-01-19 15:54                   ` bug#7859: " Jan Djärv
2011-01-19 23:44                     ` Paul Eggert
2011-01-20  0:21                       ` Eli Zaretskii
2011-01-20  6:45                       ` Jan Djärv
2011-01-20  7:51                         ` Paul Eggert
2011-01-20 11:26                           ` Jan D.
2011-01-19 23:49                     ` Paul Eggert
2011-01-20  2:30                       ` Tom Tromey
2011-01-20  0:27                   ` Eric Blake
2011-01-23 12:39         ` Eli Zaretskii
2011-01-23 20:38           ` Paul Eggert
2011-01-24  4:08             ` Eli Zaretskii
2011-01-24 23:48               ` Paul Eggert
2011-01-25  4:02                 ` Eli Zaretskii
2011-01-26 15:43                 ` Eli Zaretskii
2011-01-27  9:22                   ` Paul Eggert [this message]
2011-01-27  9:55                     ` Eli Zaretskii
2011-01-27 10:29                       ` Bruno Haible
2011-01-28 10:09                         ` Eli Zaretskii
2011-01-28 21:06                           ` Paul Eggert
2011-01-28 22:36                             ` Eli Zaretskii
2011-01-28 22:40                               ` Eric Blake
2011-01-29  8:48                                 ` Eli Zaretskii
2011-01-29  9:32                                   ` Simon Josefsson
2011-01-29 10:24                                     ` Eli Zaretskii
2011-01-27 20:50                       ` gnulib strftime, Emacs, and nanosecond-resolution time stamps Paul Eggert
2011-01-24  6:18             ` syncing Emacs from sources maintained elsewhere Ralf Wildenhues
2011-01-29 10:04             ` Eli Zaretskii
2011-01-31  8:19               ` Paul Eggert
2011-01-29 12:53     ` Eli Zaretskii
2011-01-29 15:46       ` Chong Yidong

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=4D413962.4060603@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bug-gnulib@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).