From: "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: `notmuch setup` replaces `~/.notmuch-config` instead of truncating it
Date: Wed, 17 Nov 2010 00:17:45 +0200 [thread overview]
Message-ID: <AANLkTi=WWdknHgSseeAqoBb2JFNjaGfEvK6XKePAgxOH@mail.gmail.com> (raw)
In-Reply-To: <4CE2ECA1.3030108@fifthhorseman.net>
On Tue, Nov 16, 2010 at 22:42, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> On 11/16/2010 03:37 PM, Daniel Kahn Gillmor wrote:
>> On 11/16/2010 03:26 PM, Ciprian Dorin, Craciun wrote:
>>> So in the light of the above quoted "glitches", my question is:
>>> due to the small chance of a power loss happening right when we write
>>> such a small file, doesn't the inconvenience weight more than the
>>> (fairly remote probable) file loss?
>>
>> What inconvenience? The inconvenience of writing the code correctly?
>
> Ah sorry -- on re-reading, i see you're probably referring to the
> inconvenience of breaking hardlinks, dropping permissions, ACLs and
> other metadata.
Yes, exactly this is what I'm referring to: the meta-data that is
not copied when a new file is created.
> That's an open question, as far as i'm concerned. it'd be nice if there
> was a way to "clone" a file's permissions and metadata to get the best
> of both worlds. maybe someone knows some tricks to do that?
>
> --dkg
next prev parent reply other threads:[~2010-11-16 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 13:33 `notmuch setup` replaces `~/.notmuch-config` instead of truncating it Ciprian Dorin, Craciun
2010-11-16 13:38 ` Jameson Rollins
2010-11-16 15:38 ` Daniel Kahn Gillmor
2010-11-16 19:09 ` Carl Worth
2010-11-16 20:26 ` Ciprian Dorin, Craciun
2010-11-16 20:37 ` Daniel Kahn Gillmor
2010-11-16 20:42 ` Daniel Kahn Gillmor
2010-11-16 22:17 ` Ciprian Dorin, Craciun [this message]
2010-11-16 22:16 ` Ciprian Dorin, Craciun
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=WWdknHgSseeAqoBb2JFNjaGfEvK6XKePAgxOH@mail.gmail.com' \
--to=ciprian.craciun@gmail.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).