From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] HACKING
Date: Sat, 07 Dec 2013 12:13:04 +0100 [thread overview]
Message-ID: <87eh5o52yn.fsf@gnu.org> (raw)
In-Reply-To: <20131206083745.GA12004@jocasta.intra> (John Darrington's message of "Fri, 6 Dec 2013 09:37:46 +0100")
John Darrington <john@darrington.wattle.id.au> skribis:
> commit feae92498356789d19883424cc078e8e8827626b
> Author: John Darrington <jmd@gnu.org>
> Date: Sun Dec 1 08:28:54 2013 +0100
>
> HACKING: Updated advice about possible errors in ./bootstrap process.
>
> Commit ff1cbb95383b25cf1d6b533c8a046329ee53d1db made errors due to
> missing pkg.m4 appear earlier rather than later. This commit updates
> the HACKING file to reflect that.
Thanks, I’ve applied something similar.
Ludo’.
prev parent reply other threads:[~2013-12-07 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 8:37 [PATCH] HACKING John Darrington
2013-12-07 11:13 ` 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=87eh5o52yn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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).