From: ng0 <ng0@we.make.ritual.n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: curl releases and download - package location to add
Date: Sun, 24 Jul 2016 16:50:29 +0000 [thread overview]
Message-ID: <87r3ajyo8a.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87poq3cews.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 24 Jul 2016 16:02:43 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hello!
>
> [- curl-release@haxx.se]
>
> ng0 <ng0@we.make.ritual.n0.is> skribis:
>
>> I'm one of the developers who maintain GNU Guix, the package
>> manager and its GNU System (GuixSD).
>
> I think wording like “I’m a contributor to GNU Guix” might be less
> ambiguous (“maintain” might lead the reader to think that you
> “represent” the project.)
That is true… I did not think of the difference between
maintainer and contributor. I am sorry.
> You did not ask anything in your message, so it’s not clear to me what
> you want exactly. Did you want them to mention Guix on their web site?
>
> My 2¢,
> Ludo’.
To me the wording of the website[0] on which this address was listed
read for me like this should be obvious when they get messages
like this at this specific address.
Shall I rephrase and sent the message again?
[0]: Bottom of https://curl.haxx.se/download.html
--
♥Ⓐ ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-07-24 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 16:54 curl releases and download - package location to add ng0
2016-07-24 14:02 ` Ludovic Courtès
2016-07-24 16:50 ` ng0 [this message]
2016-07-24 16:57 ` Andreas Enge
2016-07-24 17:02 ` Leo Famulari
2016-07-24 18:01 ` ng0
2016-07-24 20:05 ` Andreas Enge
2016-07-25 9:24 ` Ludovic Courtès
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=87r3ajyo8a.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
--cc=ludo@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.