From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38280) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHnbc-0002mp-G9 for guix-patches@gnu.org; Wed, 31 Oct 2018 06:20:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gHnbY-0007Ug-21 for guix-patches@gnu.org; Wed, 31 Oct 2018 06:20:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:52018) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gHnbW-0007Th-GT for guix-patches@gnu.org; Wed, 31 Oct 2018 06:20:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gHnbW-00062X-3v for guix-patches@gnu.org; Wed, 31 Oct 2018 06:20:02 -0400 Subject: [bug#33214] Patch Tracker no. 33214 Resent-Message-ID: MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?G=C3=A1bor?= Boskovits Date: Wed, 31 Oct 2018 11:18:53 +0100 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Lakshmi Prasannakumar Cc: 33214@debbugs.gnu.org Hello Laksmi, Lakshmi Prasannakumar ezt =C3=ADrta (id=C5=91pont: 2018. okt. 31., Sze, 10:30): > > Hi G=C3=A1bor, > > I'm sending an email with the tracker no. cc-ing both of you. This is the= number I received from the bug tracker. Below is the link from the bug tra= cker. > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D33214 > Thanks for the tracker id. I did not find it because I was looking in a slightly wrong way (I was looking for r-weight) :) In guix, there is a convention on the commit messages, you can see it in git log, it is also documented in the coding conventions. In this case it should look something like this: gnu: Add r-weight. * gnu/packages/cran.scm (r-weight): New variable. You can modify the commit message using git commit --amend, then create a new patch and send that. I will test this package, and report back later. > Do let me know if I need to commit again and create a patch file, as this= was the first time I committed, I'm not completely sure if it was right or= not. > > Thanks, > Lakshmi Prasannakumar > Bangalore