From: "Sébastien Kirche" <sebastien.kirche.no@spam.free.fr.invalid>
Subject: Re: lost uidvalidity
Date: Fri, 28 Jan 2005 11:51:51 +0100 [thread overview]
Message-ID: <m2mzutq114.fsf@seki.fr> (raw)
In-Reply-To: <iluacqu91oq.fsf@latte.josefsson.org>
Le 27 Jan 2005, Simon Josefsson s'est exprimé ainsi :
> It is only saved if you quit the group, though. Perhaps C-u 1 RET on
> the group, and then q to quit the summary buffer, will help?
Too late to test for it.
> But I don't believe the uidvalidity group parameter influence header
> retrieval, so I think you should look elsewhere for the reason for the
> "retrieving headers" message. (Although, arguable, a missing
> uidvalidity _should_ lead to a cache invalidate.)
I simply copied the value of uidvalidity from my home computer and it seemed
to fix that every opening headers retrieving.
I hope that i won't have problems with two clients with same uidvalidity...
--
Sébastien Kirche
prev parent reply other threads:[~2005-01-28 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 16:45 Sébastien Kirche
2005-01-26 13:02 ` Simon Josefsson
2005-01-26 13:25 ` Sébastien Kirche
2005-01-27 18:17 ` Simon Josefsson
2005-01-28 10:51 ` Sébastien Kirche [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2mzutq114.fsf@seki.fr \
--to=sebastien.kirche.no@spam.free.fr.invalid \
--cc=sebastien.kirche@free.fr \
/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).