From: Eli Zaretskii <eliz@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-pretest-bug@gnu.org, lennart.borgman@gmail.com,
monnier@iro.umontreal.ca
Subject: Re: 23.0.60; uid problems on w32
Date: Sun, 30 Mar 2008 11:24:21 -0400 [thread overview]
Message-ID: <E1JfzOP-0001sy-MC@fencepost.gnu.org> (raw)
In-Reply-To: <47EF9D73.4000508@gnu.org> (message from Jason Rumney on Sun, 30 Mar 2008 15:02:27 +0100)
> Date: Sun, 30 Mar 2008 15:02:27 +0100
> From: Jason Rumney <jasonr@gnu.org>
> CC: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-pretest-bug@gnu.org,
> lennart.borgman@gmail.com
>
> Eli Zaretskii wrote:
> > Actually, one (in `struct passwd') is `signed int', the other (in
> > `struct stat') is `signed short'. Darn that MS-supplied stat.h!
> >
> > Yes, this is probably the reason.
> >
> > Jason, do we have any good reasons to use `struct stat' as declared on
> > the system header?
>
> Not that I'm aware, but I'm probably less familiar with that code than
> you are.
OK, I will add this to my todo. Thanks.
next prev parent reply other threads:[~2008-03-30 15:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 22:09 23.0.60; uid problems on w32 Lennart Borgman (gmail)
2008-03-30 0:54 ` Jason Rumney
2008-03-30 1:07 ` Lennart Borgman (gmail)
2008-03-30 1:16 ` Jason Rumney
2008-03-30 1:23 ` Lennart Borgman (gmail)
2008-03-30 5:31 ` Eli Zaretskii
2008-03-30 11:00 ` Lennart Borgman (gmail)
2008-03-30 4:14 ` Stefan Monnier
2008-03-30 5:40 ` Eli Zaretskii
2008-03-30 14:02 ` Jason Rumney
2008-03-30 15:24 ` Eli Zaretskii [this message]
2008-03-31 14:28 ` Jason Rumney
2008-03-31 19:29 ` Eli Zaretskii
2008-04-05 15:27 ` Eli Zaretskii
2008-04-05 15:12 ` Eli Zaretskii
2008-04-05 18:40 ` Stefan Monnier
2008-04-05 19:09 ` Eli Zaretskii
2008-04-05 15:08 ` Eli Zaretskii
2008-03-30 14:48 ` Jason Rumney
2008-03-30 15:23 ` Eli Zaretskii
2008-03-30 15:27 ` Lennart Borgman (gmail)
2008-03-30 18:39 ` Eli Zaretskii
2008-03-30 20:33 ` Lennart Borgman (gmail)
2008-03-30 20:48 ` Eli Zaretskii
2008-03-30 20:54 ` Lennart Borgman (gmail)
2008-03-31 3:07 ` Eli Zaretskii
2008-03-31 8:41 ` Jason Rumney
2008-03-31 12:23 ` Lennart Borgman (gmail)
2008-03-31 12:44 ` Jason Rumney
2008-03-31 15:49 ` Lennart Borgman (gmail)
2008-03-31 16:04 ` Jason Rumney
2008-03-31 19:28 ` Eli Zaretskii
2008-03-31 16:09 ` Razi Shaban
2008-03-31 19:37 ` Eli Zaretskii
2008-03-31 19:47 ` Lennart Borgman (gmail)
2008-03-31 20:36 ` Eli Zaretskii
2008-03-31 20:42 ` Lennart Borgman (gmail)
2008-04-01 3:07 ` Eli Zaretskii
2008-03-30 5:30 ` Eli Zaretskii
2008-03-30 5:23 ` Eli Zaretskii
2008-03-30 11:11 ` Lennart Borgman (gmail)
2008-03-31 21:52 ` thdox
2008-04-01 3:31 ` Eli Zaretskii
2008-04-01 15:53 ` Lennart Borgman (gmail)
2008-04-02 18:14 ` thdox
2008-04-02 18:21 ` Lennart Borgman (gmail)
2008-04-05 15:28 ` Eli Zaretskii
2008-04-05 20:44 ` Jason Rumney
2008-04-06 9:16 ` thdox
2008-04-07 23:12 ` thdox
2008-04-07 23:15 ` Lennart Borgman (gmail)
2008-04-08 18:26 ` Eli Zaretskii
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=E1JfzOP-0001sy-MC@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=jasonr@gnu.org \
--cc=lennart.borgman@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).