From: Cyril Roelandt <tipecaml@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Cross-compilation fixes
Date: Sat, 14 Dec 2013 18:30:38 +0100 [thread overview]
Message-ID: <52AC95BE.5020101@gmail.com> (raw)
In-Reply-To: <20131214172255.GA1707@intra>
On 12/14/2013 06:22 PM, John Darrington wrote:
> On Sat, Dec 14, 2013 at 05:55:53PM +0100, Ludovic Courtès wrote:
> John Darrington <john@darrington.wattle.id.au> skribis:
>
> > Attached are several patches addressing cross-compilation issues,
> > culminating in a large patch affecting lots of files, moving
> > various "inputs" to "native-inputs".
>
> Could you send them inline, one message per patch? That would
> significantly ease review.
>
> I'll see what I can do.
>
> (‘git format-patch’ and ‘git send-email’ can be used for that, as noted
> in HACKING.)
>
> I can't find any mention of "git send-email" in HACKING, and there appears
> to be no such command. At least not in the git that I have installed (1.7.10.4)
>
> J'
>
Depending on your distribution, it might be part of another package
(git-email in Debian, for instance). It is an extremely nice tool. You
can generate a patch series by doing:
$ git format-patch <commit>
This will generate a bunch of files called 0001-commit-title,
0002-commit-title and so on. Then just do:
$ git send-email --to guix-devel@gnu.org --in-reply-to <message-id of
your first message> 000*.patch
And we'll get all your patches in a nice thread :)
I'll take a look at the HACKING file and add the necessary instructions.
Cyril.
next prev parent reply other threads:[~2013-12-14 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 15:06 [PATCH] Various issues John Darrington
2013-12-14 16:55 ` Cross-compilation fixes Ludovic Courtès
2013-12-14 17:22 ` John Darrington
2013-12-14 17:30 ` Cyril Roelandt [this message]
2013-12-14 17:39 ` 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
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=52AC95BE.5020101@gmail.com \
--to=tipecaml@gmail.com \
--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 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).