From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: add lispf4 (Update)
Date: Thu, 18 Feb 2016 12:48:11 +0100 [thread overview]
Message-ID: <idjbn7e5jes.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87bn7ep7tz.fsf_-_@grrlz.net>
Nils Gillmann <niasterisk@grrlz.net> writes:
> I contacted the author of the port (Blake McBride), it will take
> some weeks until he can help, but he'll definitely help to
> debug the issue. As it currently is quasi-broken, should I open a
> bug about it with details, content of this message and that I am
> working on it, close it once it is fixed?
Since the package is already in Guix and is not usable, I think it would
be good to keep track of it by opening a Guix bug report.
When it finally can be fixed with an update to the package definition
the commit message should contain a line “Fixes: #1234.” or similar.
~~ Ricardo
next prev parent reply other threads:[~2016-02-18 11:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 18:45 [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-06 22:14 ` Leo Famulari
2016-02-07 0:01 ` Nils Gillmann
2016-02-07 10:59 ` Ricardo Wurmus
2016-02-07 11:09 ` Ricardo Wurmus
2016-02-07 15:09 ` Nils Gillmann
2016-02-18 11:38 ` [PATCH] gnu: add lispf4 (Update) Nils Gillmann
2016-02-18 11:48 ` Ricardo Wurmus [this message]
2016-02-07 16:50 ` [PATCH] gnu: add lispf4 Nils Gillmann
2016-02-08 0:36 ` Leo Famulari
2016-02-08 11:17 ` Nils Gillmann
2016-02-08 20:14 ` Leo Famulari
2016-02-09 1:31 ` Nils Gillmann
2016-02-09 7:16 ` Efraim Flashner
2016-02-09 10:30 ` Nils Gillmann
2016-02-10 5:36 ` Leo Famulari
2016-02-10 13:48 ` Nils Gillmann
2016-02-12 4:00 ` Leo Famulari
2016-02-14 3:52 ` Nils Gillmann
2016-02-14 8:10 ` Ricardo Wurmus
2016-02-14 21:31 ` Nils Gillmann
2016-02-14 21:36 ` Ricardo Wurmus
2016-02-14 4:05 ` Nils Gillmann
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=idjbn7e5jes.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=niasterisk@grrlz.net \
/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.