From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH]: gnu: gnurl: Update to 7.50.1. Date: Mon, 15 Aug 2016 20:05:20 -0400 Message-ID: <20160816000520.GA16663@jasmine> References: <87h9azqncs.fsf@we.make.ritual.n0.is> <87y44bclh5.fsf@we.make.ritual.n0.is> <20160805154952.GA19656@jasmine> <87eg636vvq.fsf@we.make.ritual.n0.is> <87invfxels.fsf@we.make.ritual.n0.is> <87inv3r9nw.fsf@we.make.ritual.n0.is> <20160815175326.GA17361@jasmine> <87eg5phayy.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60360) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZRsu-0006or-Qu for guix-devel@gnu.org; Mon, 15 Aug 2016 20:05:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bZRsq-0004FE-A8 for guix-devel@gnu.org; Mon, 15 Aug 2016 20:05:35 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:44581) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZRso-0004Bb-O2 for guix-devel@gnu.org; Mon, 15 Aug 2016 20:05:32 -0400 Content-Disposition: inline In-Reply-To: <87eg5phayy.fsf@we.make.ritual.n0.is> 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" To: ng0 Cc: guix-devel@gnu.org On Mon, Aug 15, 2016 at 11:24:37PM +0000, ng0 wrote: > Leo Famulari writes: > > Will you file a bug report with the gnurl developers about this failing > > test and reply to this email with a link to the bug report? > > yes I will do so and see who can fix it. Thank you! > > Ideally, the package update commit would include a link to the upstream > > bug report about the failing test, but I'm not going to wait for the > > link to update this. > > I see, I thought this should just be placed into comments in the package > definition. Makes sense to include it in the commit message. That's what I meant: the link should go in a code comment in the package itself.