GNU bug report logs - #28739
[PATCH 0/5] Update python{,2}-a*

Previous Next

Full log

Message #14 received at 28739 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Cyril Roelandt <tipecaml <at> gmail.com>
Cc: 28739 <at> debbugs.gnu.org
Subject: Re: [bug#28739] [PATCH 0/5] Update python{,2}-a*
Date: Mon, 9 Oct 2017 15:53:19 -0400

[Message part 1 (text/plain, inline)]

On Mon, Oct 09, 2017 at 09:49:13PM +0200, Cyril Roelandt wrote:
> Hehe. So, to give a bit more context: I'm trying to write an updated
> version of my Guix backend for tox (the Python virtual environment
> manager). One of the issues I have when trying it on real-world projects
> is that our Python libraries are a bit outdated.

Yeah, I'm glad you're working on this.

> If it's OK with everybody, I'd like to push the simplest patches (those
> that only change the version and the hash) without going through a
> review first. WDYT?

Sure, I think it's fine. HACKING says:

For patches that just add a new package, and a simple one, it’s OK to
commit [without going through the code review process], if you’re
confident (which means you successfully built it in a chroot setup, and
have done a reasonable copyright and license auditing.)  Likewise for
package upgrades, except upgrades that trigger a lot of rebuilds (for
example, upgrading GnuTLS or GLib.)  We have a mailing list for commit
notifications (guix-commits <at> gnu.org), so people can notice.  Before
pushing your changes, make sure to run ‘git pull --rebase’.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.