From: Troy Hinckley <comms@dabrev.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drew.adams@oracle.com, stefankangas@gmail.com, corwin@bru.st,
charmitro@gmail.com, emacs-devel@gnu.org, larsi@gnus.org
Subject: Re: [External] : Re: Emacs 28.3 RC1 testing
Date: Tue, 4 Apr 2023 07:46:41 -0500 [thread overview]
Message-ID: <2cb859bb-979f-4721-b315-f1d1cda4b69d@Spark> (raw)
In-Reply-To: <83tty6884u.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
Hi Stefan,
What can I do to help with the 28.3 release process?
On Mar 27, 2023 at 11:35 AM -0500, Eli Zaretskii <eliz@gnu.org>, wrote:
> > Date: Mon, 27 Mar 2023 10:12:35 -0600
> > From: Troy Hinckley <comms@dabrev.com>
> > Cc: Charalampos Mitrodimas <charmitro@gmail.com>,
> > "emacs-devel@gnu.org" <emacs-devel@gnu.org>, Lars
> > Ingebrigtsen <larsi@gnus.org>
> >
> > Who needs to sign off to do the release? Is that only Eli or Stefan?
>
> Stefan was working on releasing Emacs 28.3.
[-- Attachment #2: Type: text/html, Size: 976 bytes --]
prev parent reply other threads:[~2023-04-04 12:46 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
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 [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
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=2cb859bb-979f-4721-b315-f1d1cda4b69d@Spark \
--to=comms@dabrev.com \
--cc=charmitro@gmail.com \
--cc=corwin@bru.st \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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).