From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0. Date: Wed, 22 Apr 2015 17:54:01 +0200 Message-ID: <20150422155401.GA6017@debian.math.u-bordeaux1.fr> References: <1429524721-21449-1-git-send-email-iyzsong@gmail.com> <87618p19aw.fsf@gnu.org> <20150421211500.GA6274@debian> <87pp6x6s6v.fsf@netris.org> <20150422120642.GB4297@debian.math.u-bordeaux1.fr> <87d22w6w9f.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50270) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ykwya-0004F4-Ny for guix-devel@gnu.org; Wed, 22 Apr 2015 11:54:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YkwyU-0008Ay-Om for guix-devel@gnu.org; Wed, 22 Apr 2015 11:54:12 -0400 Received: from mout.kundenserver.de ([212.227.126.131]:56158) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YkwyU-0008AQ-Fp for guix-devel@gnu.org; Wed, 22 Apr 2015 11:54:06 -0400 Content-Disposition: inline In-Reply-To: <87d22w6w9f.fsf@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Mark H Weaver Cc: guix-devel@gnu.org On Wed, Apr 22, 2015 at 11:03:08AM -0400, Mark H Weaver wrote: > Well, fair enough :) However, since I reverted the libidn-1.30 update > and cancelled all the associated jobs on Hydra, the argument actually > does apply, although that was not clear from this message alone. Definitely, these two needed to go together. > There's an easy solution for this: click on the little "Compare to..." > button near the top right corner of the evaluation page, and select > "Jobset gnu:master". More generally, visit: > http://hydra.gnu.org/eval/?compare= > where and are evaluation IDs. Nifty trick, thanks for sharing! > Does this make sense? It does. Now, I would still like some guidelines for what to commit to master and what to core-updates, that we could possibly write down in HACKING (and update when the hydra situation changes). Does something like "If you modify PACKAGE from base.scm, or 'guix refresh -l PACKAGE' shows that >= N packages are affected, then commit to core-updates" make sense? If yes, what should be the value of N? If not, what would be a better idea? Andreas