git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Mark Rada <marada@uwaterloo.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] tests: make all test files executable
Date: Sun, 4 Oct 2009 09:40:22 -0400	[thread overview]
Message-ID: <20091004134022.GA14209@sigill.intra.peff.net> (raw)
In-Reply-To: <1762B430-2DC0-48F5-8C34-8428F9145A1E@mailservices.uwaterloo.ca>

On Sun, Oct 04, 2009 at 09:18:20AM -0400, Mark Rada wrote:

> >Ah, nevermind. The problem is that your patch was word-wrapped, making
> >the second "diff --git" line bogus. It would have been nice to have it
> >print a warning instead of silently ignoring that bit of the patch.
> >
> I didn't have format=flowed buggering things up this time, so I don't
> quite understand the problem; could you please explain with more
> details?

Sure. The patch is perfect except for one line. What should have been:

diff --git a/t/t9501-gitweb-standalone-http-status.sh b/t/t9501-gitweb-standalone-http-status.sh

was wrapped to:

diff --git a/t/t9501-gitweb-standalone-http-status.sh
b/t/t9501-gitweb-standalone-http-status.sh

I have no idea how you did that, though. :)

It looks like you send with Thunderbird. How do you get the diff content
into the email? Is it possible that it wraps the content after you have
gotten it there?

> When I try to apply the patch from a saved copy of the e-mail, I get
> the following error:
> 
> 	# git am ~/Downloads/\[PATCH\]\ tests_\ make\ all\ test\ files\
> executable.eml
> 	Patch format detection failed.
> 	zsh: exit 1     git am
> 
> The difference between the patch created by format-patch and the saved
> e-mail is just some e-mail header information. Is that a different error
> than what you were getting? I'm not sure what I'm doing wrong here, help
> would be appreciated.

Yeah, that's totally different than the problem I was having. I save to
an mbox from mutt, which "git am" understands just fine. I'd have to see
what was in your .eml file to know why "git am" couldn't figure it out
(and it might be a good test case, as "git am" has recently learned to
accept more mailbox formats).

-Peff

  reply	other threads:[~2009-10-04 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  1:59 [PATCH] tests: make all test files executable Mark Rada
2009-10-02  8:01 ` Jeff King
2009-10-02  8:39   ` Jeff King
2009-10-04 13:18     ` Mark Rada
2009-10-04 13:40       ` Jeff King [this message]
2009-10-05  1:25         ` Mark Rada
2009-10-05  9:59           ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2009-10-06  1:46 Mark Rada
2009-10-06 10:00 ` 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=20091004134022.GA14209@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=marada@uwaterloo.ca \
    /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).