From: Olaf Hering <olaf@aepfle.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: missing handling of "No newline at end of file" in git am
Date: Wed, 15 Feb 2017 12:44:30 +0100 [thread overview]
Message-ID: <20170215114430.GD16249@aepfle.de> (raw)
In-Reply-To: <20170214215103.7d5e5f4c@probook.ubnt.lan>
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
On Tue, Feb 14, Olaf Hering wrote:
> How would I debug it?
One line is supposed to be longer than 998 chars, but something along
the way truncated it and corrupted the patch. No idea why the error
today is different from the error yesterday.
'git pull' has to be used in this case.
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-02-15 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 20:11 missing handling of "No newline at end of file" in git am Olaf Hering
2017-02-14 20:40 ` Junio C Hamano
2017-02-14 20:51 ` Olaf Hering
2017-02-15 11:44 ` Olaf Hering [this message]
2017-02-20 8:06 ` Eric Wong
2017-02-14 20:47 ` 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=20170215114430.GD16249@aepfle.de \
--to=olaf@aepfle.de \
--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).