From: David Leverton <levertond@googlemail.com>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Agenda for the meeting of December 7th, 2009
Date: Sun, 6 Dec 2009 14:27:52 +0000 [thread overview]
Message-ID: <200912061427.52295.levertond@googlemail.com> (raw)
In-Reply-To: <19227.47687.44279.886421@a1i15.kph.uni-mainz.de>
On Sunday 06 December 2009 14:05:59 Ulrich Mueller wrote:
> The spec first proposed was along the lines "mtime is updated if
> (and only if) the package manager modifies the file" [1], but the
> Paludis party raised objections that this was not specific enough.
> But see below about "common sense".
It's not specific enough because it gives the implementer no way of knowing
which files don't require preservation, and therefore, which are safe to
modify without preserving the mtime. Common sense doesn't come into it.
next prev parent reply other threads:[~2009-12-06 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 7:40 [gentoo-council] Agenda for the meeting of December 7th, 2009 Denis Dupeyron
2009-12-06 11:48 ` Ulrich Mueller
2009-12-06 12:40 ` David Leverton
2009-12-06 14:05 ` Ulrich Mueller
2009-12-06 14:27 ` David Leverton [this message]
2009-12-06 17:18 ` Robin H. Johnson
2009-12-06 19:04 ` Denis Dupeyron
2009-12-06 19:51 ` Ned Ludd
2009-12-07 3:48 ` Zac Medico
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=200912061427.52295.levertond@googlemail.com \
--to=levertond@googlemail.com \
--cc=gentoo-council@lists.gentoo.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