all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org, Bastien Guerry <bzg@gnu.org>
Subject: Re: [BUG] list.orgmode.org managed to parse a message in future: 2023-10-29 [9.6.1 (release_9.6.1-223-gc8d20d @ /home/yantar92/.emacs.d/straight/build/org/)]
Date: Mon, 06 Feb 2023 10:12:55 +0000	[thread overview]
Message-ID: <87h6vzcdaw.fsf@localhost> (raw)
In-Reply-To: <87y1pccfkj.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> Kyle Meyer <kyle@kyleam.com> writes:
>
>> Eric replied with a patch that resolved the issue.  I've installed it.
>
> Thanks!
> I think I saw the "future" thread disappearing briefly, but it is again
> there on top of https://list.orgmode.org/.

I no longer see the problem and, as per discussion in public inbox ML,
we will leave future date displayed below thread link as is.

Fixed.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2023-02-06 10:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 10:55 [BUG] list.orgmode.org managed to parse a message in future: 2023-10-29 [9.6.1 (release_9.6.1-223-gc8d20d @ /home/yantar92/.emacs.d/straight/build/org/)] Ihor Radchenko
2023-02-03 11:38 ` Jean Louis
2023-02-05 18:41   ` Greg Minshall
2023-02-07 18:57     ` Jean Louis
2023-02-10 11:06       ` Greg Minshall
2023-02-04 16:02 ` Max Nikulin
2023-02-04 17:32 ` future value for Date header can pin thread to top of $inbox/ " Kyle Meyer
2023-02-04 17:37   ` [BUG] " Kyle Meyer
2023-02-04 21:42   ` Kyle Meyer
2023-02-05 15:11     ` Ihor Radchenko
2023-02-06 10:12       ` Ihor Radchenko [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=87h6vzcdaw.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.