From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: gnu: clang-from-llvm: Clean up share/clang folder.
Date: Wed, 28 Nov 2018 10:52:00 +0100 [thread overview]
Message-ID: <87va4hlebj.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20181128093247.GA28059@macbook41>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
Sorry for the mess, that was an obvious mistake, I should have thought twice
about it before pushing.
Efraim, let me know if you can't push, then I'll do it.
That said, I wonder why we need so many old Clangs. For instance, I see we only
use clang-3.9.1 for DarkTable and c-reduce. c-reduce could be updated according
to the comment. And DarkTable builds fine with clang 7 according to Arch Linux.
(Maybe they are wrong.)
Either way, I think it would be a good idea to always comment why some specific
version of a program has to be used, lest we see a plethora of versions grow,
which makes maintenance a bit harder sometimes.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-11-28 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181126135350.20543.84585@vcs0.savannah.gnu.org>
[not found] ` <20181126135351.C5B4420427@vcs0.savannah.gnu.org>
2018-11-27 23:35 ` 03/03: gnu: clang-from-llvm: Clean up share/clang folder Mark H Weaver
2018-11-28 9:32 ` Efraim Flashner
2018-11-28 9:52 ` Pierre Neidhardt [this message]
2018-11-28 10:23 ` Pierre Neidhardt
2018-11-28 10:54 ` Efraim Flashner
2018-11-28 12:43 ` Pierre Neidhardt
2018-11-28 13:23 ` 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=87va4hlebj.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=efraim@flashner.co.il \
--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.