From: Corwin Brust <corwin@bru.st>
To: Charalampos Mitrodimas <charmitro@gmail.com>
Cc: Drew Adams <drew.adams@oracle.com>,
Troy Hinckley <comms@dabrev.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>
Subject: Re: [External] : Re: Emacs 28.3 RC1 testing
Date: Sat, 18 Mar 2023 11:58:45 -0500 [thread overview]
Message-ID: <CAJf-WoSbjDNR5q9ef6VxQD5yRDhQ1BHp4pYRKsSJ94v6FF4h6A@mail.gmail.com> (raw)
In-Reply-To: <20230318164948.n3vvjo6utpflaqsw@Charalamposs-MacBook-Air.local>
On Sat, Mar 18, 2023 at 11:49 AM Charalampos Mitrodimas
<charmitro@gmail.com> wrote:
>
> On Sat, Mar 18, 2023 at 04:27:21PM +0000, Drew Adams wrote:
> > The latest RC I see at https://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28/
> > is RC1, dated 2023-02-19.
>
> Hey Drew, I believe 28.3-rc1 is the one that Corwin is refering as "pre-release".
You are correct - 28.3-rc1 is the pre-release I was referring to. I
suspect Drew mistyped as he's got the dates correct for when that was
posted.
I use this sorting, so the most recently posted are on top:
https://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28/?C=M;O=D
next prev parent reply other threads:[~2023-03-18 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <06c78bbd-0e25-4bd3-bb58-d13e1c5003ac@Spark>
2023-03-17 22:52 ` Emacs 28.3 RC1 testing Troy Hinckley
2023-03-18 10:23 ` Charalampos Mitrodimas
2023-03-18 15:51 ` Corwin Brust
2023-03-18 16:27 ` [External] : " Drew Adams
2023-03-18 16:49 ` Charalampos Mitrodimas
2023-03-18 16:55 ` Drew Adams
2023-03-18 16:58 ` Corwin Brust [this message]
2023-03-18 19:30 ` Drew Adams
2023-03-18 21:08 ` Corwin Brust
2023-03-27 16:12 ` Troy Hinckley
2023-03-27 16:35 ` Eli Zaretskii
2023-04-04 12:46 ` Troy Hinckley
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=CAJf-WoSbjDNR5q9ef6VxQD5yRDhQ1BHp4pYRKsSJ94v6FF4h6A@mail.gmail.com \
--to=corwin@bru.st \
--cc=charmitro@gmail.com \
--cc=comms@dabrev.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.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.