From: Tim Howes via Bug reports for GNU Guix <bug-guix@gnu.org>
To: divoplade <d@divoplade.fr>, 43093@debbugs.gnu.org
Subject: bug#43093: emacs-ess is broken by emacs 27.1
Date: Tue, 8 Sep 2020 12:24:40 -0700 [thread overview]
Message-ID: <8277b0d1-8874-1b8a-7a9f-4e517322e9c4@lavabit.com> (raw)
In-Reply-To: <596f84e01551f5c7c6059d5bb247b77ea14b13ac.camel@divoplade.fr>
On 9/7/2020 2:52 PM, divoplade wrote:
> Le lundi 07 septembre 2020 à 23:19 +0200, divoplade a écrit :
>> Sorry, I don't know how to make a patch.
>>
> By trying to make one, I noticed that you have already sent a patch. I
> don't know why I did not recieve it. I am still clueless about a lot of
> things here.
>
> Anyway, you forgot to update the license. It is now GPLv3+.
>
> Best regards,
>
> divoplade
>
That's alright, I should have cc'd you with the patch, but forgot since
I was using git send-email.
I started a separate thread here for this patch. There still seems to be
a problem with it, as the build sometimes fails due to a file locking
issue. And it was suggested that I should version it as a revision of
18.02.2 instead of this versioning scheme.
https://issues.guix.gnu.org/43208
Thanks also for the note about the license. I'll update that accordingly.
-Tim
next prev parent reply other threads:[~2020-09-08 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 20:07 bug#43093: emacs-ess is broken by emacs 27.1 divoplade
2020-09-04 14:44 ` bug#43093: Is Emacs 27.1 that breaks emacs-ess? zimoun
2020-09-04 15:26 ` divoplade
2020-09-04 17:00 ` Mark H Weaver
2020-09-04 18:09 ` zimoun
2020-09-04 18:25 ` bug#43093: emacs-ess is broken by emacs 27.1 Tim Howes via Bug reports for GNU Guix
2020-09-07 21:19 ` divoplade
2020-09-07 21:43 ` divoplade
2020-09-07 21:52 ` divoplade
2020-09-08 19:24 ` Tim Howes via Bug reports for GNU Guix [this message]
2020-09-04 23:25 ` bug#43093: [PATCH] gnu: emacs-ess: Update to 20200903.1516 Tim Howes via Bug reports for GNU Guix
2020-09-28 3:28 ` Maxim Cournoyer
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=8277b0d1-8874-1b8a-7a9f-4e517322e9c4@lavabit.com \
--to=bug-guix@gnu.org \
--cc=43093@debbugs.gnu.org \
--cc=d@divoplade.fr \
--cc=timhowes@lavabit.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/guix.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.