From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 18068@debbugs.gnu.org
Subject: bug#18068: LINUX_MODULE_DIRECTORY needs trailing slash
Date: Wed, 23 Jul 2014 22:28:28 +0200 [thread overview]
Message-ID: <8761inx1jn.fsf@gnu.org> (raw)
In-Reply-To: <87d2cv4zta.fsf@yeeloong.lan> (Mark H. Weaver's message of "Wed, 23 Jul 2014 15:53:21 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>> Commits 906f704 and 4a8b4c2 address both issues. Thanks!
>
> Alas, this seems to have broken the linux-libre builds on all platforms.
I had forgotten one, it is fixed with 94b1342.
Thanks for the heads-up!
Ludo’.
prev parent reply other threads:[~2014-07-23 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 4:37 bug#18068: LINUX_MODULE_DIRECTORY needs trailing slash Mark H Weaver
2014-07-21 16:12 ` Ludovic Courtès
2014-07-23 2:22 ` Mark H Weaver
2014-07-23 17:10 ` Ludovic Courtès
2014-07-23 19:53 ` Mark H Weaver
2014-07-23 20:28 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761inx1jn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=18068@debbugs.gnu.org \
--cc=mhw@netris.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).