From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org, jasonr@gnu.org
Subject: Re: 23.0.60; uid problems on w32
Date: Sun, 30 Mar 2008 13:00:33 +0200 [thread overview]
Message-ID: <47EF72D1.4020201@gmail.com> (raw)
In-Reply-To: <E1Jfq8k-0002Fn-TH@fencepost.gnu.org>
Eli Zaretskii wrote:
>> Date: Sun, 30 Mar 2008 03:07:42 +0200
>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
>> Cc: emacs-pretest-bug@gnu.org
>>
>> I tested with Cygwin on my pc and it looks like expected there. All uid
>> values are equal: (nth 2 attrs), (user-uid) in server-ensure-safe-dir
>> and the output from cygwin id. ls -l shows the same name as cygwin id.
>
> What do you mean by ``tested with Cygwin''? Was it a Cygwin build of
> Emacs or something else?
Sorry. I meant that I tested "ls -l" and "id" in Cygwin. Emacs is a w32
build done with gcc.
next prev parent reply other threads:[~2008-03-30 11:00 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) [this message]
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
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=47EF72D1.4020201@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=jasonr@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).