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/db-wg@ripe.net/

[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 ]

Job Snijders job at instituut.net
Thu Apr 17 14:55:44 CEST 2014

On Thu, Apr 17, 2014 at 01:58:39PM +0200, Denis Walker wrote:

> If we implement attributes with generated values is there any point in
> keeping the "changed:" attribute at all?

You are right. "last-modified:" makes "changed:" entirely redundant,
would only serve to still my sense of nostalgia. I support removing the
"changed:" attribute from all RIPE objects.

Kind regards,

Job

• 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 ]