This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] last-modified:, a succesor to changed:
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu Apr 17 15:06:17 CEST 2014
On Thu, Apr 17, 2014 at 01:58:39PM +0200, Denis Walker wrote: Dear All > If we implement attributes with generated values is there any point in > keeping the "changed:" attribute at all? > > It: > -is user set to a vast range of dates (user's choice) with as many or few > instances as you wish > -is unreliable and possibly miss-leading to anyone else > -will become, even if correct, a duplication of both the generated values > and --list-versions output > -requires mandatory email address > -invites abuse > > Maybe it could be deprecated if the proposed attributes are implemented? Although I see some idea behind keeping the "changed:" attribute (at least as optional one), I fully support making it deprecated if the proposal of implementing last-modified: would be accepted. Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski at polsl.pl
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]