From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: cox.katherine.e+guix@gmail.com, 68571-done@debbugs.gnu.org,
andrew@trop.in
Subject: bug#68571: [PATCH 0/2] Update Emacs to 29.2
Date: Sun, 21 Jan 2024 09:38:59 +0100 [thread overview]
Message-ID: <91c1e2ae301bd232e64ca927e68af0c14a48c562.camel@gmail.com> (raw)
In-Reply-To: <87h6j7b89n.fsf@gmail.com>
Am Samstag, dem 20.01.2024 um 23:49 -0500 schrieb Maxim Cournoyer:
> Hello,
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
> > Hi Guix,
> >
> > this series updates emacs to 29.2. Given that it's a minor
> > release, it should be fine on master once the the substitutes have
> > built. Anyhow, it is currently based on master, because the
> > ongoing work on emacs-team is… ongoing, but in theory we could do
> > the good old mergeroo.
> >
> > WDYT?
> >
> > Liliana Marie Prikler (2):
> > gnu: emacs-minimal: Set upstream-name to “emacs”.
> > gnu: emacs-minimal: Update to 29.2.
> >
>
> LGTM! Thank you.
Thanks, pushed.
Cheers
(On that note, should I include the Reviewed-by: line next time?)
next prev parent reply other threads:[~2024-01-21 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 19:46 [bug#68571] [PATCH 0/2] Update Emacs to 29.2 Liliana Marie Prikler
2024-01-18 19:44 ` [bug#68571] [PATCH 1/2] gnu: emacs-minimal: Set upstream-name to “emacs” Liliana Marie Prikler
2024-01-18 19:45 ` [bug#68571] [PATCH 2/2] gnu: emacs-minimal: Update to 29.2 Liliana Marie Prikler
2024-01-21 4:49 ` [bug#68571] [PATCH 0/2] Update Emacs " Maxim Cournoyer
2024-01-21 8:38 ` Liliana Marie Prikler [this message]
2024-01-21 9:12 ` Liliana Marie Prikler
2024-03-29 9:15 ` [bug#68571] Emacs 29.3 emergency security-fix release Adam Porter
2024-03-29 9:17 ` [bug#68571] [PATCH 0/2] Update Emacs to 29.2 Cayetano Santos via Guix-patches via
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=91c1e2ae301bd232e64ca927e68af0c14a48c562.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=68571-done@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=maxim.cournoyer@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/guix.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).