git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Nathan W. Panike" <nathan.panike@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to efficiently find where a patch applies?
Date: Thu, 5 May 2011 16:17:18 -0400	[thread overview]
Message-ID: <20110505201718.GA2533@sigill.intra.peff.net> (raw)
In-Reply-To: <20110505201204.GA31572@nwp-laptop>

On Thu, May 05, 2011 at 03:12:05PM -0500, Nathan W. Panike wrote:

> The patches were emailed as raw diffs, not as format-patch messages, so I
> thought git-am was not applicable. Also, I was applying the patches to the git
> repository on behalf of local colleagues when they ran into problems using
> 'git-apply'.

Git-am is basically just a wrapper around git-apply that will split an
email message into a raw diff and a commit message. If you have raw
diffs in an email, it may handle them OK, or it may be simple enough to
massage them into the right form.

As far as I know, there isn't a convenient way to get "git apply" to do
the same merge magic for a raw diff that "git am -3" does. It should be
possible, as the only relevant input is the raw diff; I just don't think
anybody has bothered to do it.

> I did not want to deal with merge conflicts---my colleagues can
> handle the conflicts themselves. So a clean merge was optimal from my
> perspective.

Ah, that makes more sense. I have been in a similar "helping people with
git" situation myself.

> > Wow, dynamically generating awk using perl. That's a new one for me. :)
> You might say it is awk-ward.

Ouch. :)

-Peff

      reply	other threads:[~2011-05-05 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 18:17 How to efficiently find where a patch applies? Nathan W. Panike
2011-05-05 19:55 ` Jeff King
2011-05-05 20:12   ` Nathan W. Panike
2011-05-05 20:17     ` Jeff King [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

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

  git send-email \
    --in-reply-to=20110505201718.GA2533@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=nathan.panike@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.
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).