From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 31018@debbugs.gnu.org
Subject: [bug#31018] [PATCH] Improvements for our Emacs build system and fixes.
Date: Fri, 13 Apr 2018 21:28:21 -0400 [thread overview]
Message-ID: <87r2nio9u2.fsf@gmail.com> (raw)
In-Reply-To: <faec7bc3.AM8AAAStCIYAAAAAAAAAAAPHPfsAAAACwQwAAAAAAAW9WABa0RYW@mailjet.com> (Arun Isaac's message of "Sat, 14 Apr 2018 02:11:46 +0530")
Arun Isaac <arunisaac@systemreboot.net> writes:
> This is a very long patchset, and it's getting a little unwieldy to
> review. I'll start by pushing some of the simpler patches to
> master. Then, we can come back and discuss the rest.
Sounds reasonable, as long as you understand that some packages will
break (well, they are silently broken right now already) if the build
system patches and the package fixes are not merged at the same time.
Thank you for helping with this review :)
Maxim
next prev parent reply other threads:[~2018-04-14 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 15:57 [bug#31018] [PATCH] Improvements for our Emacs build system and fixes Maxim Cournoyer
2018-04-13 20:41 ` Arun Isaac
[not found] ` <faec7bc3.AM8AAAStCIYAAAAAAAAAAAPHPfsAAAACwQwAAAAAAAW9WABa0RYW@mailjet.com>
2018-04-14 1:28 ` Maxim Cournoyer [this message]
2018-04-14 16:51 ` Arun Isaac
[not found] ` <9925e912.AM4AAAS8QCUAAAAAAAAAAAPHPfsAAAACwQwAAAAAAAW9WABa0jGH@mailjet.com>
2018-04-17 2:59 ` [bug#31018] [PATCHv2] " Maxim Cournoyer
2018-04-20 17:46 ` Arun Isaac
2018-05-03 16:32 ` bug#31018: " Arun Isaac
2018-05-03 16:54 ` [bug#31018] " Arun Isaac
[not found] ` <5b6467d3.AMMAAAVkQu8AAAAAAAAAAAPHPfsAAAACwQwAAAAAAAW9WABa2idv@mailjet.com>
2018-05-07 12:13 ` Maxim Cournoyer
2018-05-07 14:14 ` Arun Isaac
[not found] ` <handler.31018.D31018.152536517825664.notifdone@debbugs.gnu.org>
2018-05-07 12:21 ` [bug#31018] closed (Re: [bug#31018] [PATCHv2] Improvements for our Emacs build system and fixes.) 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=87r2nio9u2.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=31018@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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.