From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>,
Efraim Flashner <efraim@flashner.co.il>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: core-updates, let’s go!
Date: Sun, 31 Dec 2017 16:07:21 +0100 [thread overview]
Message-ID: <87a7xzaqc6.fsf@fastmail.com> (raw)
In-Reply-To: <20171231121416.5df20c3b@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> I'd like to get the patch
>
> [bug#29856] [PATCH core-updates] guix: python-build-system: Modify ".py" files in-place.
>
> into this core-updates cycle. What do you all think?
We already have a substantial amount of Python changes on core-updates,
so we could save ourselves some trouble by adding this when there's less
"congestion" in case of any problems.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-12-31 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 10:27 core-updates, let’s go! Ludovic Courtès
2017-12-31 10:32 ` Efraim Flashner
2017-12-31 11:14 ` Danny Milosavljevic
2017-12-31 12:20 ` Danny Milosavljevic
2017-12-31 15:07 ` Marius Bakke [this message]
2017-12-31 17:27 ` Ricardo Wurmus
2018-01-02 18:12 ` change to the wrap-program procedure (was: core-updates, let’s go!) Hartmut Goebel
2018-01-02 19:01 ` Ricardo Wurmus
2018-01-02 19:19 ` change to the wrap-program procedure Hartmut Goebel
2018-01-02 20:47 ` Ricardo Wurmus
2017-12-31 14:44 ` core-updates, let’s go! Marius Bakke
2018-01-01 17:12 ` Ludovic Courtès
2018-01-01 19:08 ` Efraim Flashner
2018-01-03 18:35 ` Leo Famulari
2018-01-03 20:06 ` Leo Famulari
2018-01-03 19:34 ` Leo Famulari
2018-01-18 3:50 ` Leo Famulari
2018-01-20 0:51 ` core-updates: SELinux Leo Famulari
2018-01-28 12:32 ` Ricardo Wurmus
2018-01-20 20:57 ` core-updates, let’s go! Kei Kebreau
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=87a7xzaqc6.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=dannym@scratchpost.org \
--cc=efraim@flashner.co.il \
--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).