all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Troy Sankey <sankeytms@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: updating many haskell packages
Date: Mon, 6 Feb 2017 16:47:26 +0100	[thread overview]
Message-ID: <20170206154726.GA10414@jasmine> (raw)
In-Reply-To: <148635860347.5455.1039513310657824569@what>

[-- Attachment #1: Type: text/plain, Size: 448 bytes --]

On Mon, Feb 06, 2017 at 12:23:23AM -0500, Troy Sankey wrote:
> I wonder how I should send these patches after I'm all done.  git
> send-email?  That seems crazy.

Dozens of patches in their own messages is a little hard to work with as
a reviewer. But, you can put them all in one patch file that is trivial
to apply to my Git tree:

$ git format-patch your-branch..master --stdout > patch-series.patch

And on my end:

$ git am patch-series.patch

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-02-06 15:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  5:23 updating many haskell packages Troy Sankey
2017-02-06 15:47 ` Leo Famulari [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-06  8:03 Federico Beffa
2017-02-06  8:13 ` Federico Beffa
2017-02-15 19:07   ` Troy Sankey
2017-02-17 16:43     ` Ricardo Wurmus
2017-02-06 15:23 ` Troy Sankey
2017-02-06 20:34   ` Federico Beffa
2017-02-06 21:00     ` Troy Sankey
2017-02-15 19:31       ` Troy Sankey
2017-02-17  8:00         ` Federico Beffa
2017-02-17 17:47           ` Troy Sankey
2017-02-18  9:43             ` Federico Beffa
2017-02-18 17:40               ` Troy Sankey
2017-02-18 20:23                 ` Federico Beffa
2017-02-19 19:21                 ` Troy Sankey

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170206154726.GA10414@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=sankeytms@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.