Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jochen Küpper" <jochen=W2i0oK7yYu0+t3nig+EZI7NAH6kLmebB@public.gmane.org>
Subject: Re: Saving attachments with a leading dot
Date: Thu, 02 Oct 2003 21:56:53 +0200	[thread overview]
Message-ID: <86vfr7qupm.fsf@doze.rijnh.nl> (raw)
In-Reply-To: <4n8yo38qe4.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 02 Oct 2003 14:07:31 -0400")

On Thu, 02 Oct 2003 14:07:31 -0400 Ted Zlatanov wrote:

Ted> On Mon, 29 Sep 2003, harder=YSGFQ8SKJZVDPfheJLI6IQ@public.gmane.org wrote:

>> Jochen Küpper <jochen=W2i0oK7yYu0+t3nig+EZI7NAH6kLmebB@public.gmane.org> writes:
>> 
>>> And what is up with filesystems that use different mechanisms or
>>> don't have them, i.e. AFS, FAT based stuff, ... ? Should Gnus even
>>> care what filesystem the file is written too? (In the spirit of
>>> this discussion, it has to.)
>> 
>> Windows doesn't have an executable bit, right?

Ted> No, but it does have some attributes (none related to this).

Cygwin does have Unix file permissions, for example. I am not sure
*that* works on FAT?

On Thu, 02 Oct 2003 14:10:42 -0400 Ted Zlatanov wrote:

Ted> I'm saying that's not something Emacs supports right now. The
Ted> shell should handle it, I think. In any case, I don't think an
Ted> attachment should ever be saved with permissions other than 0600,
Ted> 0640, or 0644.

At least 444 is perfectly valid, and some people also like 664 / 666
for most of their files...

Ted> I think Gnus should try to give the file proper permissions, but
Ted> it shouldn't lose sleep over it. Sometimes it's not possible.

+1

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)




  reply	other threads:[~2003-10-02 19:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-23 23:39 Jesper Harder
2003-09-24 10:38 ` Ted Zlatanov
2003-09-25  3:24   ` Jesper Harder
2003-09-25  4:22     ` Ted Zlatanov
2003-09-25  5:49       ` Jochen Küpper
2003-09-29  3:28         ` Jesper Harder
2003-10-02 18:07           ` Ted Zlatanov
2003-10-02 19:56             ` Jochen Küpper [this message]
2003-10-03  1:35             ` Jesper Harder
2003-10-03 14:04               ` Benjamin Riefenstahl
2003-10-02 18:10         ` Ted Zlatanov
2003-09-24 13:53 ` Benjamin Riefenstahl
2003-09-24 14:40   ` Ted Zlatanov
2003-09-24 15:11     ` Benjamin Riefenstahl
2003-09-24 16:03       ` Ted Zlatanov
2003-09-24 16:16         ` Benjamin Riefenstahl
2003-09-24 17:45           ` Ted Zlatanov
2003-09-24 15:48 ` Reiner Steib
2003-09-24 16:11   ` Benjamin Riefenstahl
2003-09-25 14:40     ` Reiner Steib
2003-09-25  3:23   ` Jesper Harder
2003-09-25  8:44 ` Hanak David
2003-09-29  3:20   ` Jesper Harder
2003-10-17 17:31     ` Lars Magne Ingebrigtsen
2003-10-18 16:43       ` Jesper Harder
2003-10-18 16:50         ` Lars Magne Ingebrigtsen
2003-10-18 20:04           ` Jesper Harder
2003-10-18 23:17           ` Jesper Harder
2003-10-19 11:14             ` Lars Magne Ingebrigtsen

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=86vfr7qupm.fsf@doze.rijnh.nl \
    --to=jochen=w2i0ok7yyu0+t3nig+ezi7nah6klmebb@public.gmane.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.
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 NNTP newsgroup(s).