From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Andrew Tropin <andrew@trop.in>, Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 65000@debbugs.gnu.org
Subject: [bug#65000] [PATCH] gnu: emacs-next: Update to 29.1.
Date: Mon, 14 Aug 2023 17:04:39 +0200 [thread overview]
Message-ID: <fd014adafb3f0fc73e01351a489e368ea53f9810.camel@gmail.com> (raw)
In-Reply-To: <878rae6igl.fsf@trop.in>
Am Montag, dem 14.08.2023 um 14:12 +0400 schrieb Andrew Tropin:
> On 2023-08-14 07:45, Liliana Marie Prikler wrote:
>
> > Am Mittwoch, dem 02.08.2023 um 14:20 +0400 schrieb Andrew Tropin:
> > > I agree, let's take this to emacs package in emacs-team branch
> > > and
> > > merge back to master after depended packages are built.
> > Pushed the emacs-brach team and merge master back in yesterday in
> > the
> > evening.
>
> Cool, thank you very much for working on it!
>
> > Let's wait a bit for CI.
>
> Does push to emacs-team trigger a CI?
>
> I can't find it in https://ci.guix.gnu.org/ UI.
何？どうして？
I literally just found out thanks to your mail that emacs-team is no
longer on Cuirass. There should be better communication on this…
next prev parent reply other threads:[~2023-08-14 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 0:00 [bug#65000] [PATCH] gnu: emacs-next: Update to 29.1 Tobias Geerinckx-Rice via Guix-patches via
2023-08-01 20:27 ` Liliana Marie Prikler
2023-08-01 21:10 ` Tobias Geerinckx-Rice via Guix-patches via
2023-08-02 4:25 ` Liliana Marie Prikler
2023-08-02 10:20 ` Andrew Tropin
2023-08-14 5:45 ` Liliana Marie Prikler
2023-08-14 10:12 ` Andrew Tropin
2023-08-14 15:04 ` Liliana Marie Prikler [this message]
2023-08-14 15:31 ` Liliana Marie Prikler
2023-08-14 17:49 ` Andrew Tropin
2023-08-02 18:30 ` [bug#65000] [PATCH emacs-team v2] gnu: emacs: " Liliana Marie Prikler
2023-08-23 10:06 ` [bug#65000] [PATCH] gnu: emacs-next: " Ludovic Courtès
2023-08-23 12:13 ` Andrew Tropin
2023-08-23 16:54 ` bug#65000: " Liliana Marie Prikler
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=fd014adafb3f0fc73e01351a489e368ea53f9810.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=65000@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=me@tobias.gr \
/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).