9front - general discussion about 9front
 help / color / mirror / Atom feed
From: theinicke@bss-wf.de
To: 9front@9front.org
Subject: upas/fs plumb modify for self-made flag changes
Date: Sat, 1 Feb 2020 13:24:25 +0100	[thread overview]
Message-ID: <C544019E2842D505054CDED1920449AE@yourdomain.dom> (raw)

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

Currently upas/fs plumbs modify messages only if the flag changes are made by another imap connection. If the flag changes are made within the running upas/fs no modify message is plumbed.

Assuming this is not intentionally and we want to get a modify plumb message after flags were changed in running upas/fs the attached patch fixes this by making sure to send a modify for pending changes upon mbox sync.

The modify could be plumbed earlier, but this way it costs us almost nothing and changed flags from outside upas/fs are noticed in the same time interval anyway.

--
Tobias Heinicke

[-- Attachment #2.1: Type: text/plain, Size: 326 bytes --]

from postmaster@9pi:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Disposition: attachment; filename=upasfs.patch
	Content-Type: text/plain; charset="US-ASCII"
	Content-Transfer-Encoding: 7bit

[-- Attachment #2.2: upasfs.patch.suspect --]
[-- Type: application/octet-stream, Size: 306 bytes --]

diff -r 8857059a1805 sys/src/cmd/upas/fs/fs.c
--- a/sys/src/cmd/upas/fs/fs.c	Fri Jan 31 09:25:39 2020 -0800
+++ b/sys/src/cmd/upas/fs/fs.c	Sat Feb 01 13:22:38 2020 +0100
@@ -1197,6 +1197,7 @@
 			mb->modflags(mb, m, f);
 		m->flags = f;
 		m->cstate |= Cidxstale;
+		m->cstate |= Cmod;
 	}
 	return nil;
 }

             reply	other threads:[~2020-02-01 12:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 12:24 theinicke [this message]
2020-02-02 22:18 ` [9front] " ori
2020-02-03  9:12   ` theinicke
2020-02-05  6:11     ` ori
2020-02-05 21:49       ` theinicke
2020-02-05 22:11         ` ori
2020-02-05 22:16       ` Lyndon Nerenberg
2020-02-06  0:41         ` Stanley Lieber
2020-02-06  0:41         ` Stanley Lieber

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=C544019E2842D505054CDED1920449AE@yourdomain.dom \
    --to=theinicke@bss-wf.de \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).