From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Testing needed for lzip substitutes!
Date: Mon, 17 Jun 2019 11:22:00 +0200 [thread overview]
Message-ID: <87tvco1s93.fsf@gnu.org> (raw)
In-Reply-To: <87zhmjizki.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sat, 15 Jun 2019 00:15:09 +0200")
Hello,
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> When replying to a days-old message, please consider quoting the
>> relevant bits. :-)
>
> Hmmm, actually, why would it be a matter of age? I think it's only a
> matter of context, and someone browsing the archive years later will not
> mind if a reply was sent 1 day or 1 week later. All that matters is the
> full thread. In my opinion a single email
> is useless when not in the context of the entire thread.
> So I believe that it makes more sense for email clients to use
> threading than not.
>
> Or maybe that's not what you meant :p
What I meant is that it’s easier for me (and for others I believe) if
there’s a bit of context. Gnus doesn’t display the whole thread by
default, so I have to explicitly ask it to display it, etc.
In a way, it’s a MUA issue, and mu4e-conversation seems to be a great
solution to that problem, but not everyone uses it yet. ;-)
> So I've tried with both qualif and ci, and qualif did not publish any
> substitutes for me. It works on ci.guix.gnu.org though, and I get
> lzipped substitutes! Hooray!
Yay! qualif is gone now.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-06-17 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 8:56 Testing needed for lzip substitutes! Ludovic Courtès
2019-06-06 10:03 ` Pierre Neidhardt
2019-06-11 10:35 ` Pierre Neidhardt
2019-06-11 18:43 ` Ludovic Courtès
2019-06-14 22:15 ` Pierre Neidhardt
2019-06-17 9:22 ` Ludovic Courtès [this message]
2019-06-17 9:37 ` Pierre Neidhardt
2019-06-17 11:12 ` Vincent Legoll
2019-06-17 11:32 ` Pierre Neidhardt
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=87tvco1s93.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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.