From: Chris Packham <judge.packham@gmail.com>
To: git@vger.kernel.org
Subject: [RFC PATCH 0/1] am: bug report and new patch format support
Date: Wed, 3 Sep 2014 21:35:18 +1200 [thread overview]
Message-ID: <1409736919-22341-1-git-send-email-judge.packham@gmail.com> (raw)
Hi List,
When I first tried to apply a patch someone gave me I got the following
errors.
$ git am patch.patch
tr: write error: Broken pipe
tr: write error
Patch format detection failed.
The patch itself was generated from gitk and while I'd seen the format
detection problem before but the tr errors were new to me. I haven't
looked at the tr problem yet but the gitk thing had been bugging me for
a while so here's a patch that understands the format generated by gitk.
Documentation/git-am.txt | 3 ++-
git-am.sh | 35 +++++++++++++++++++++++++++++++++++
2 files changed, 37 insertions(+), 1 deletion(-)
Chris Packham (1):
am: add gitk patch format
next reply other threads:[~2014-09-03 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 9:35 Chris Packham [this message]
2014-09-03 9:35 ` [RFC PATCH 1/1] am: add gitk patch format Chris Packham
2014-09-03 9:59 ` Chris Packham
2014-09-03 10:18 ` [RFC PATCH 0/1] am: bug report and new patch format support Chris Packham
2014-09-03 22:21 ` [RFC PATCHv2 0/2] am: bug fix " Chris Packham
2014-09-03 22:21 ` [RFC PATCHv2 1/2] am: add gitk patch format Chris Packham
2014-09-03 23:19 ` Junio C Hamano
2014-09-04 0:46 ` Chris Packham
2014-09-04 17:21 ` Junio C Hamano
2014-09-04 22:47 ` Chris Packham
[not found] ` <CAPc5daWip1dQ5Or6hzmdjoBUStusvs-jK0ODNuzAotNfM5BLbQ@mail.gmail.com>
2014-09-05 1:23 ` Chris Packham
2014-09-05 18:29 ` Junio C Hamano
2014-09-05 21:54 ` Chris Packham
2014-09-03 22:21 ` [RFC PATCHv2 2/2] am: avoid re-directing stdin twice Chris Packham
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=1409736919-22341-1-git-send-email-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
/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).