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 <j...@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.
