From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Tobias Geerinckx-Rice <me@tobias.gr>, 39599@debbugs.gnu.org
Subject: [bug#39599] [PATCH 1/4] build-system: Add copy-build-system.
Date: Fri, 21 Feb 2020 13:06:13 +0100 [thread overview]
Message-ID: <87lfow4022.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87ftf4xipf.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> I removed *all* leading whitespace in
> af51d01a8aa8d7cf529173bdb64392f14eb21962 and this fixes the
> problem. In future, avoid it altogether. It clashes with the
> rest of the file even when it doesn't break anything.
Thanks for the fix.
> If you're using some kind of fancy-texinfo-mode please disable it,
> although I wonder who writes a mode that breaks things so badly
> :-p
I don't, I just indented manually. It was impossible to read otherwise.
Well, Texinfo is a bit tedious, I guess we have to leave with it.
Crazy that "guix pull" broke and not "make". I wonder why "guix pull"
is so sensitive.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-21 12:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 12:51 [bug#39599] [PATCH 0/2] New build system: copy-build-system Pierre Neidhardt
2020-02-14 12:53 ` [bug#39599] [PATCH 1/2] build-system: Add copy-build-system Pierre Neidhardt
2020-02-14 12:53 ` [bug#39599] [PATCH 2/2] gnu: gcide: Use the copy-build-system Pierre Neidhardt
2020-02-14 13:39 ` [bug#39599] [PATCH 1/2] build-system: Add copy-build-system Giovanni Biscuolo
2020-02-16 13:16 ` Pierre Neidhardt
2020-02-17 11:12 ` [bug#39599] [PATCH 1/4] " Pierre Neidhardt
2020-02-17 11:12 ` [bug#39599] [PATCH 2/4] gnu: gcide: Use the copy-build-system Pierre Neidhardt
2020-02-17 11:12 ` [bug#39599] [PATCH 3/4] gnu: Add clojure-wrapper Pierre Neidhardt
2020-02-17 11:12 ` [bug#39599] [PATCH 4/4] gnu: net-base: Use copy build system Pierre Neidhardt
2020-02-17 11:48 ` [bug#39599] [PATCH 1/4] build-system: Add copy-build-system Mathieu Othacehe
2020-02-20 9:47 ` Ricardo Wurmus
2020-02-20 10:00 ` Pierre Neidhardt
2020-02-20 1:06 ` Alex Griffin
2020-02-20 8:40 ` Pierre Neidhardt
2020-02-20 8:44 ` Mathieu Othacehe
[not found] ` <87pne95krx.fsf@ambrevar.xyz>
2020-02-20 17:09 ` Julien Lepiller
2020-02-20 18:00 ` Pierre Neidhardt
2020-02-21 9:53 ` Pierre Neidhardt
2020-02-21 10:43 ` Nicolas Goaziou
2020-02-21 11:07 ` Pierre Neidhardt
2020-02-21 11:43 ` Nicolas Goaziou
2020-02-21 12:04 ` Pierre Neidhardt
2020-02-21 11:50 ` Tobias Geerinckx-Rice via Guix-patches via
2020-02-21 12:06 ` Pierre Neidhardt [this message]
2020-02-21 3:37 ` [bug#39599] Jack Hill
2020-02-21 3:37 ` [bug#39599] [PATCH v2] gnu: Add gnome-shell-extension-paperwm Jack Hill
2020-02-21 14:34 ` Alex Griffin
2020-02-21 16:22 ` Jack Hill
2020-02-21 18:48 ` Alex Griffin
2020-02-21 18:51 ` Jack Hill
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=87lfow4022.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=39599@debbugs.gnu.org \
--cc=me@tobias.gr \
/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).