git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nathan W. Panike" <nathan.panike@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Allow format-patch to create patches for merges
Date: Mon, 26 Jan 2009 15:46:42 -0600	[thread overview]
Message-ID: <d77df1110901261346k7951809cv240ccddc22bf4884@mail.gmail.com> (raw)
In-Reply-To: <20090126204543.GF27604@coredump.intra.peff.net>

I have not used the bundle stuff, but yes, it seems to be a better fit
for what I am trying to do.

Thanks,

Nathan Panike

On Mon, Jan 26, 2009 at 2:45 PM, Jeff King <peff@peff.net> wrote:
> On Mon, Jan 26, 2009 at 10:27:18AM -0600, Nathan W. Panike wrote:
>
>> I think I have an unusual workflow where my patch makes sense,
>> although it probably does not for the vast majority of git users.  I
>> regularly use 3 machines: S, L, and H.  I keep my work synchronized by
>> using git.  Normally, I fetch from S to L or to H, depending on which
>> machine I am working on at the moment.  I also push from L or H to S.
>> I sporadically lose connectivity to S, so I have a hook in the repo on
>> S to send a backup email to me on mail server M, which has a more
>> reliable connection.  This email also serves as a  reminder when I
>
> Have you considered sending a bundle instead of a patch in the backup
> email? That is the more exact equivalent of a push (i.e., it preserves
> your actual commits, sha1 and all).
>
> -Peff
>

  reply	other threads:[~2009-01-26 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26 14:04 [PATCH] Allow format-patch to create patches for merges Nathan W. Panike
2009-01-26 15:36 ` Johannes Schindelin
2009-01-26 16:27   ` Nathan W. Panike
2009-01-26 20:45     ` Jeff King
2009-01-26 21:46       ` Nathan W. Panike [this message]
2009-01-26 18:33   ` Junio C Hamano

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=d77df1110901261346k7951809cv240ccddc22bf4884@mail.gmail.com \
    --to=nathan.panike@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.
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 NNTP newsgroup(s).