all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: lispf4: Remove unused inputs key.
Date: Tue, 13 Sep 2016 19:21:34 +0000	[thread overview]
Message-ID: <87intz7ght.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20160913190030.GA5986@jasmine>

Leo Famulari <leo@famulari.name> writes:

> On Mon, Sep 12, 2016 at 01:57:56PM +0000, ng0 wrote:
>> * gnu/packages/lisp.scm (lispf4)[arguments]: Remove unused
>> inputs from 'install phase.
>> [source](file-name): Append -checkout to the file-name.
>
> Pushed! Now to make it work :)

Thanks!

Well... I think I have to actually learn to write C and FORTRAN and not
only read and understand. The author seemed not very interested in
helping, they have either forgotten that they wanted to check the bug
out or it was just to satisfy me for the moment.

Or maybe we have someone here who can read and write FORTRAN and
C... FORTRAN is only needed to understand the original source, the
language itself is in C.

-- 
              ng0

  reply	other threads:[~2016-09-13 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 13:57 [PATCH 1/2] gnu: Add femtolisp ng0
2016-09-12 13:57 ` [PATCH 2/2] gnu: lispf4: Remove unused inputs key ng0
2016-09-13 19:00   ` Leo Famulari
2016-09-13 19:21     ` ng0 [this message]
2016-09-13 19:40 ` [PATCH 1/2] gnu: Add femtolisp Leo Famulari
  -- strict thread matches above, loose matches on Subject: below --
2016-09-13 19:04 ng0
2016-09-13 19:04 ` [PATCH 2/2] gnu: lispf4: Remove unused inputs key ng0

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=87intz7ght.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.