all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: 01/01: gnu: Add niftilib.
Date: Mon, 20 Mar 2017 06:57:11 +0100	[thread overview]
Message-ID: <20170320055711.GA19992@jocasta.intra> (raw)
In-Reply-To: <87d1dd5775.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 816 bytes --]

On Sun, Mar 19, 2017 at 04:42:54PM -0400, Mark H Weaver wrote:
     john@darrington.wattle.id.au (John Darrington) writes:
     
     > jmd pushed a commit to branch master
     > in repository guix.
     >
     > commit 21122bd79e7f9b0b5349ffffe2c146bace7205dc
     > Author: John Darrington <jmd@gnu.org>
     > Date:   Tue Mar 7 07:59:21 2017 +0100
     >
     >     gnu: Add niftilib.
     >     
     >     * gnu/packages/image.scm (niftilib): New variable.
     
     Did you post this for review?  Please see below for comments.

Yes.  One person reviewed it before I pushed.   You are the second person to 
have reviewed it afterwards - making a total of three.    So it would seem
that the best way to get one's patches reviewed is to push them!

Thanks for the comments anyway.
     

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2017-03-20  5:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170318142616.19421.55332@vcs0.savannah.gnu.org>
     [not found] ` <20170318142617.B58A320DF8@vcs0.savannah.gnu.org>
2017-03-19 20:42   ` 01/01: gnu: Add niftilib Mark H Weaver
2017-03-19 21:03     ` Kei Kebreau
2017-03-20 10:56       ` Alex Kost
2017-03-20  5:57     ` John Darrington [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170320055711.GA19992@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=guix-devel@gnu.org \
    --cc=jmd@gnu.org \
    --cc=mhw@netris.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.