From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 02/24] gnu: Add ghc-paths.
Date: Wed, 08 Apr 2015 14:10:18 +0200 [thread overview]
Message-ID: <87lhi2yg5x.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPNCQ-=AWOgkJqoSdMVYdkpqE84U84tmsbe4f=7q4bcaOA@mail.gmail.com> (Federico Beffa's message of "Wed, 8 Apr 2015 13:44:46 +0200")
Federico Beffa <beffa@ieee.org> skribis:
> On Wed, Apr 8, 2015 at 10:01 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>>> + (synopsis
>>> + "Knowledge of GHC's installation directories")
>>> + (description
>>> + "Knowledge of GHC's installation directories.")
>>
>> Please expound a little bit. Otherwise OK.
>
> Thanks for reviewing all of these!
>
> The problem with this and some other libraries is that the library
> doesn't have an official home-page (apart from a source repository
> which doesn't include anything other than the source). The description
> is taken one-to-one from the Cabal file and I don't really know how I
> can expand the description.
Often there’s a README or manual that gives a better overview, but yeah,
I don’t mean that you should spend another 10 hours on this. ;-) So if
you find a paragraph that’s clearer, that’s nice, otherwise it’s OK.
> The Cabal file of some other libraries like, e.g., ghc-network, give
> an, IMO, too detailed description (sometimes even with a code
> snippet):
Agreed, something like this one is overly detailed.
Ludo’.
prev parent reply other threads:[~2015-04-08 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 16:38 [PATCH 02/24] gnu: Add ghc-paths Federico Beffa
2015-04-08 8:01 ` Ludovic Courtès
2015-04-08 11:44 ` Federico Beffa
2015-04-08 12:10 ` Ludovic Courtès [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=87lhi2yg5x.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=beffa@ieee.org \
--cc=guix-devel@gnu.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.