Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Subject: Re: 'g' transfers a lot of data
Date: Wed, 06 Oct 2010 11:22:47 +0200	[thread overview]
Message-ID: <sa339sj8yl4.fsf@cigue.easter-eggs.fr> (raw)
In-Reply-To: <m3fwwkflim.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 05 Oct 2010 22:10:57 +0200")

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

On Tue, Oct 05 2010, Lars Magne Ingebrigtsen wrote:

> Let's see...  yeah, it syncs 100 articles "too much", and 100 lines is
> about 3K, så 300K sounds right.  The point of doing 100 articles "too
> much" is to get any flag changes done by other MUAs, and the idea is
> that it's most likely to happen to quite recent messages.
>
> This is 100 flags on articles we've seen before -- not new articles.
>
> But perhaps 100 is too much?  25 might be more reasonable?

If I understand correctly, that seems a very dangerous behaviour. You
mean that if I put/remove the \Seen flags on a very old mail from
another Gnus instance, the other one will not see it?

Maybe 100 is not enough actually?
How others MUA plays with that?

(Sorry if I misunderstand something :-)

-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-10-06  9:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 11:30 Julien Danjou
2010-10-05 16:55 ` Lars Magne Ingebrigtsen
2010-10-05 18:55   ` Julien Danjou
2010-10-05 20:10     ` Lars Magne Ingebrigtsen
2010-10-06  9:22       ` Julien Danjou [this message]
2010-10-06 10:33         ` Steinar Bang
2010-10-07 19:41         ` Lars Magne Ingebrigtsen
2010-10-08  9:31           ` Julien Danjou

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=sa339sj8yl4.fsf@cigue.easter-eggs.fr \
    --to=julien@danjou.info \
    --cc=ding@gnus.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).