From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH v2] git-am: indicate where a failed patch is to be found.
Date: Fri, 13 Jul 2012 18:46:03 -0400 [thread overview]
Message-ID: <5000A52B.3090003@windriver.com> (raw)
In-Reply-To: <7vipdr8mch.fsf@alter.siamese.dyndns.org>
On 12-07-13 03:58 PM, Junio C Hamano wrote:
> Paul Gortmaker <paul.gortmaker@windriver.com> writes:
>
>> If git am fails to apply something, the end user may need
>> to know where to find the patch. This is normally known for
>> a single patch, but if the user is processing a mbox with
>> many patches, they may not have a single broken out patch
>> handy. So, provide a helpful hint as to where they can
>> find the patch to do some sort of manual fixup, if we
>> are processing a mbox with more than one patch in it.
>
> I would rather see this done even for a single patch mbox. The
OK, I got the opposite impression from your prev. mail when
you mentioned that I hadn't limited the message output at all.
I'm fine with the changes you've proposed below, and can squash that
into a v3 and resend again.
Paul.
--
> patch that was fed to "git apply" by "git am" and failed to apply is
> that one, not the one in the mbox you gave "git am". The latter may
> be ungrokkable with GNU patch or "git apply", if the original was
> sent in Quoted-Printable and such MIME funnies, which is the whole
> point of having a separate file there for "git am", instead of
> feeding the original.
>
> I am not sure if we should limit $patch_format to mbox, but I think
> showing this unconditionally regardless of mbox/stgit/hg will teach
> the user only one location to remember, so perhaps like this?
>
> Documentation/config.txt | 3 +++
> git-am.sh | 4 ++--
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 0e1168c..b1f0a75 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -143,6 +143,9 @@ advice.*::
> Advice shown when you used linkgit:git-checkout[1] to
> move to the detach HEAD state, to instruct how to create
> a local branch after the fact.
> + amWorkDir::
> + Advice that shows the location of the patch file when
> + linkgit:git-am[1] fails to apply it.
> --
>
> core.fileMode::
> diff --git a/git-am.sh b/git-am.sh
> index dc48f87..f1ae932 100755
> --- a/git-am.sh
> +++ b/git-am.sh
> @@ -834,9 +834,9 @@ did you forget to use 'git add'?"
> if test $apply_status != 0
> then
> eval_gettextln 'Patch failed at $msgnum $FIRSTLINE'
> - if test $patch_format = mbox && test "$last" -ne "1"
> + if test "$(git config --bool advice.amworkdir)" != false
> then
> - eval_gettextln "You can find the copy of the patch that failed here:
> + eval_gettextln "The copy of the patch that failed is found in:
> $dotest/patch"
> fi
> stop_here_user_resolve $this
>
next prev parent reply other threads:[~2012-07-13 22:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 15:50 [PATCH] git-am: indicate where a failed patch is to be found Paul Gortmaker
2012-07-12 17:45 ` Junio C Hamano
2012-07-12 18:32 ` Paul Gortmaker
2012-07-12 18:53 ` Junio C Hamano
2012-07-12 19:36 ` Paul Gortmaker
2012-07-12 20:00 ` Junio C Hamano
2012-07-13 17:40 ` Paul Gortmaker
2012-07-13 18:06 ` Junio C Hamano
2012-07-12 21:07 ` Junio C Hamano
2012-07-13 15:51 ` [PATCH v2] " Paul Gortmaker
2012-07-13 19:58 ` Junio C Hamano
2012-07-13 22:46 ` Paul Gortmaker [this message]
2012-07-13 23:02 ` Junio C Hamano
2012-07-12 21:18 ` [PATCH] " Nicolas Sebrecht
2012-07-12 21:55 ` Junio C Hamano
2012-07-12 20:33 ` [PATCH] " Jeff King
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=5000A52B.3090003@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).