all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Misleading messages about new versions
Date: Mon, 14 Feb 2022 07:47:53 -0500	[thread overview]
Message-ID: <jwv1r05k439.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1nJSl6-0001Qa-Ej@fencepost.gnu.org> (Richard Stallman's message of "Sun, 13 Feb 2022 23:14:40 -0500")

>   > As mentioned in the other thread (about the "dual" request), this is just
>   > a small matter of programming.
> Would you like to implement distinguishing them?

It's been in my todo for a while already, but it's never been anywhere
near the top, so I think someone else will have to do it.


        Stefan




  reply	other threads:[~2022-02-14 12:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12  3:57 Misleading messages about new versions Richard Stallman
2022-02-12  4:36 ` Stefan Monnier
2022-02-14  4:14   ` How often do we have new packages in Whichever ELPA? Richard Stallman
2022-02-14  8:33     ` Philip Kaludercic
2022-02-15  4:30       ` Richard Stallman
2022-02-15 13:27         ` Eli Zaretskii
2022-02-16  4:14           ` Richard Stallman
2022-02-16 12:18             ` Eli Zaretskii
2022-02-16 10:42         ` Rudolf Schlatte
2022-02-19  4:54           ` Richard Stallman
2022-02-16 18:28         ` Tomas Hlavaty
2022-02-16 20:07           ` Philip Kaludercic
2022-02-19  4:56             ` Richard Stallman
2022-02-17 23:14           ` Richard Stallman
2022-02-14  4:14   ` Misleading messages about new versions Richard Stallman
2022-02-14 12:47     ` Stefan Monnier [this message]
2022-02-14 17:27     ` Benjamin Riefenstahl
2022-02-14 18:31       ` Corwin Brust
2022-02-14 18:44         ` Benjamin Riefenstahl
2022-02-14 19:11       ` Jean Louis
2022-02-15  4:31       ` Richard Stallman

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=jwv1r05k439.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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.