From: Amin Bandali <bandali@gnu.org>
To: guix-devel@gnu.org
Subject: Re: [bug#42738] [PATCH v4] gnu: emacs: Update to 27.1.
Date: Fri, 28 Aug 2020 13:34:08 -0400 [thread overview]
Message-ID: <87zh6esmi7.fsf@gnu.org> (raw)
In-Reply-To: <87h7smd7t1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Brett Gilio writes:
[...]
>
> Also, are we planning to keep emacs-next and have it track 28.x or
> remove it?
>
> Brett Gilio
I would like it if it's kept. Though, if it is truly meant to track the
"next" release of Emacs, it should be pointed at the `emacs-27' branch,
as there will likely be one or more point releases in the 27 series.
On the other hand, as an Emacs developer, I would appreciate having a
package that tracks `master' that I could use. Perhaps emacs-trunk
would be a more appropriate name for that package. I know it's not
typical for guix.git to contain package definitions that point to
non-release commits; but perhaps Emacs could be an exception to that.
Thoughts?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next prev parent reply other threads:[~2020-08-28 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200819040941.32696-1-jackhill@jackhill.us>
[not found] ` <DM5PR1001MB210589E35972B5314D4D8381C5550@DM5PR1001MB2105.namprd10.prod.outlook.com>
2020-08-28 14:18 ` [PATCH v4] gnu: emacs: Update to 27.1 Ludovic Courtès
2020-08-28 14:38 ` Pierre Neidhardt
2020-08-28 17:00 ` [bug#42738] " Brett Gilio
2020-08-28 17:08 ` Jack Hill
2020-08-28 17:34 ` Amin Bandali [this message]
2020-08-28 20:04 ` Mark H Weaver
2020-08-29 10:13 ` Ludovic Courtès
2020-08-29 21:53 ` Mark H Weaver
2020-09-07 9:00 ` Ludovic Courtès
2020-08-28 18:57 ` Mark H Weaver
2020-08-28 21:10 ` Morgan Smith
2020-08-29 20:35 ` Mark H Weaver
2020-08-30 1:50 ` [bug#42738] " Brett Gilio
2020-08-29 17:19 ` Giovanni Biscuolo
2020-09-04 9:03 ` Pierre Neidhardt
[not found] ` <87pn713nr7.fsf@ambrevar.xyz>
2020-09-04 10:20 ` Giovanni Biscuolo
2020-09-07 9:44 ` Pierre Neidhardt
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=87zh6esmi7.fsf@gnu.org \
--to=bandali@gnu.org \
--cc=guix-devel@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 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).