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 ]

Marco d'Itri md at Linux.IT
Wed Apr 16 16:33:12 CEST 2014

On Apr 15, Job Snijders <job at instituut.net> wrote:

> I look forward to the group's feedback! Also, I'm interested in how
> people would use this attribute in their workflows or automation. 
No objections to an automatically enforced last-modified attribute, but 
then I would demote changed to an optional attribute to allow removing 
duplicate information.
I already use changed this way, by only keeping the last one.

-- 
ciao,
Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 648 bytes
Desc: Digital signature
URL: </ripe/mail/archives/db-wg/attachments/20140416/0a903382/attachment.sig>

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 ]