From: Gaute Hope <eg@gaute.vetsj.com>
To: Michael J Gruber <git@grubix.eu>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] introduce new.rename_tags for renamed (moved) messages
Date: Fri, 21 Sep 2018 10:34:34 +0200 [thread overview]
Message-ID: <1537518768.d9052z5zbq.astroid@strange.none> (raw)
In-Reply-To: <CAA19uiRXVEp8kPdxUw4yDvVLmG0DSXpxaKKn-ZC0uFC97uJi_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Michael J Gruber writes on September 21, 2018 10:22:
> Lastmod and (re)new tags serve different purposes, I would thank. The
> latter is a flag that can be cleared to signal that a certain job has
> been done (by whomever). Whereas, if one actor acts upon a lastmod
> change by modifying the db that will change the lastmod and (possibly)
> trigger another actor to act upon that. Different scenarios which look
> the same if you have one "actor" only.
Agreed, very useful if all scenarios can be reliably caught! Maybe it
was the "message changed without rename" that was problematic, since
offlineimap would change the X-Keywords header without renaming the
file.
- gaute
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-09-21 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 14:04 [PATCH] introduce new.rename_tags for renamed (moved) messages Michael J Gruber
2018-09-08 0:47 ` David Bremner
2018-09-18 15:32 ` [PATCH v2] " Michael J Gruber
2019-04-02 12:40 ` [PATCH] performance-tests: tests for renamed/copied files in notmuch new David Bremner
2019-04-02 12:45 ` David Bremner
2019-04-03 20:05 ` Tomi Ollila
2019-04-05 16:59 ` David Bremner
2019-04-03 1:28 ` [PATCH v2] introduce new.rename_tags for renamed (moved) messages David Bremner
2018-09-21 6:48 ` [PATCH] " Gaute Hope
[not found] ` <CAA19uiRXVEp8kPdxUw4yDvVLmG0DSXpxaKKn-ZC0uFC97uJi_Q@mail.gmail.com>
2018-09-21 8:34 ` Gaute Hope [this message]
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=1537518768.d9052z5zbq.astroid@strange.none \
--to=eg@gaute.vetsj.com \
--cc=git@grubix.eu \
--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).