unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jason Rumney'" <jasonr@gnu.org>
Cc: 819@emacsbugs.donarmstrong.com
Subject: bug#819: 23.0.60; group and owner "Everyone" - what's that about?
Date: Fri, 29 Aug 2008 20:29:15 -0700	[thread overview]
Message-ID: <002e01c90a50$94a67c50$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <48B8B5D2.603@gnu.org>

> > Just so I can understand a little better, could you 
> > elaborate? I thought that Eli was saying that with FAT32
> > it should say Everyone...Everyone everywhere.
> 
> That is what I see with a FAT32 disk too. I have no idea why you see 
> different, but it probably has something to do with your 
> local Windows configuration.
> 
> > Which is more or less (or differently?) secure, my disk or 
> > the files and folders? How is that determined/defined in the
> > Windows UI? Thx.
> >   
> 
> You are asking questions that only someone with access to 
> Windows source code could answer. It may not be different
> security, the security calls may be failing, causing Emacs
> to fall back on the old strategy of making something up.

OK, I guess the bottom line is that my Windows installation/config is in some
way, for some reason, exceptional, and this is not an Emacs bug. Thanks for
looking into it; sorry for the noise.







  reply	other threads:[~2008-08-30  3:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <u8wufaefr.fsf@gnu.org>
2008-08-29 15:00 ` bug#819: 23.0.60; group and owner "Everyone" - what's that about? Drew Adams
2008-08-29 17:46   ` Eli Zaretskii
2008-08-29 18:12     ` Drew Adams
2008-08-29 19:03       ` Jason Rumney
2008-08-29 19:22       ` Eli Zaretskii
2008-08-29 20:06         ` Drew Adams
2008-08-29 21:05           ` Stefan Monnier
2008-08-30  0:32           ` Jason Rumney
2008-08-30  2:00             ` Drew Adams
2008-08-30  2:52               ` Jason Rumney
2008-08-30  3:29                 ` Drew Adams [this message]
2008-08-30  8:15                   ` Eli Zaretskii
2008-08-30  8:56                     ` Eli Zaretskii
2008-08-30 13:55                       ` Drew Adams
2008-08-30 14:19                         ` Drew Adams
2008-08-30 14:25                         ` Eli Zaretskii
2008-08-30  8:10               ` Eli Zaretskii
2008-08-29 18:10   ` bug#819: marked as done (23.0.60; group and owner "Everyone" - what's that about?) Emacs bug Tracking System
     [not found]   ` <handler.819.D819.122003287910930.notifdone@emacsbugs.donarmstrong.com>
2008-08-29 18:44     ` bug#819: closed by Eli Zaretskii <eliz@gnu.org> (bug#819: 23.0.60; " Drew Adams
2008-08-29 19:38       ` Eli Zaretskii
2008-08-29 19:56         ` Eli Zaretskii
2008-08-29 20:10           ` Drew Adams
2008-08-29 20:07         ` Drew Adams

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='002e01c90a50$94a67c50$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=819@emacsbugs.donarmstrong.com \
    --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).