all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add r-qtl.
Date: Fri, 18 Sep 2015 11:50:24 +0200	[thread overview]
Message-ID: <87fv2cvyxr.fsf@gnu.org> (raw)
In-Reply-To: <20150918092333.GA18950@thebird.nl> (Pjotr Prins's message of "Fri, 18 Sep 2015 11:23:33 +0200")

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> Package descriptions I follow are the same as those by the software
> developers. If people care about jargon feel free to fix it.
>
> I am happy with the original descriptions from the software authors.
> Spelling it out won't help any users.

It will.  I tried to spell out the rationale for synopsis and
descriptions:

  https://lists.gnu.org/archive/html/guix-devel/2015-09/msg00445.html

I understand the frustration–after all you’ve already spent quite some
time on the package I suppose and the functional part is completely
fine.

However I think it’s important to work on maintaining a good level of
quality for these things.  It might look like nitpicking, but it’s
really the kind of polish that makes the tool more pleasant to use IMO.
We all benefit from it in the end.

So, what about sending an updated patch?  :-)

Thanks for your work,
Ludo’.

  reply	other threads:[~2015-09-18  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 14:18 [PATCH] gnu: Add r-qtl Pjotr Prins
2015-09-17 17:18 ` Mathieu Lirzin
2015-09-18  9:23   ` Pjotr Prins
2015-09-18  9:50     ` Ludovic Courtès [this message]
2015-09-18 11:51       ` Pjotr Prins
2015-09-18 14:08         ` Andreas Enge
2015-09-18 16:15           ` Pjotr Prins
2015-09-18 16:56             ` Andreas Enge
2015-09-19  0:52               ` Pjotr Prins
2015-09-20 16:52                 ` Ludovic Courtès
2015-09-21  5:17                   ` Pjotr Prins

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=87fv2cvyxr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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.