From: Ted Zlatanov <tzz@lifelogs.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 40280@debbugs.gnu.org, David Edmondson <dme@dme.org>
Subject: bug#40280: gnus-cloud doesn't do anything useful
Date: Tue, 16 Jun 2020 18:14:20 +0000 [thread overview]
Message-ID: <zh92lvyb.fsf@lifelogs.com> (raw)
In-Reply-To: <y2ow9op2.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 09 Jun 2020 16:41:29 +0000")
On Tue, 09 Jun 2020 16:41:29 +0000 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Wed, 13 May 2020 12:21:42 +0200 Mathieu Othacehe <othacehe@gnu.org> wrote:
>>> Looking at how `newer' is calculated, it compares the group timestamp
>>> from the gnus-cloud message with the current time. It's not clear to me
>>> how that test is ever going to return `nil', unless I have a version of
>>> emacs running somewhere in the future that updates gnus-cloud.
MO> I share the same conclusions on 26.3, the downloaded message is always
MO> older than current time, and nothing happens.
MO> The patch you are proposing fixes gnus cloud update for me.
TZ> I agree this is a problem and agree with David's patch.
TZ> I've pushed the patch to branch scratch/tzz/dme/bug-40280-gnus-cloud-newest
TZ> I'll merge it into master and adjust any docs needed if I can get a
TZ> second review please :)
David, Mathieu:
The patch and commit message looked good so I've pushed this.
Please confirm the fix works well for you and I'll close the bug.
Thanks
Ted
next prev parent reply other threads:[~2020-06-16 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 17:15 bug#40280: gnus-cloud doesn't do anything useful David Edmondson
2020-05-13 10:21 ` Mathieu Othacehe
2020-06-09 16:41 ` Ted Zlatanov
2020-06-16 18:14 ` Ted Zlatanov [this message]
2020-06-16 18:56 ` Basil L. Contovounesios
2020-06-17 8:13 ` David Edmondson
2020-06-17 14:10 ` Ted Zlatanov
2020-06-23 11:52 ` bug#40280: [PATCH] Fix gnus-cloud-download-all-data return value David Edmondson
2020-06-23 13:14 ` Ted Zlatanov
2020-07-19 2:39 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zh92lvyb.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=40280@debbugs.gnu.org \
--cc=dme@dme.org \
--cc=othacehe@gnu.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://git.savannah.gnu.org/cgit/emacs.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).