Hi Philip. I don't have any setting like that in either my
~/.gitconfig, or in the .git/config files. I really haven't tweaked
my git config at all.
This is a typical .git/config file:
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
url = ssh://ktan...@git.code.sf.net/p/agency/code
fetch = +refs/heads/*:refs/remotes/origin/*
remote = origin
merge = refs/heads/master
My ~/.gitconfig just has name and email settings in it.
On Wed, Nov 13, 2013 at 3:12 PM, Philip Oakley <philipoak...@iee.org> wrote:
> From: "Junio C Hamano" <gits...@pobox.com>
> To: "Ken Tanzer" <ken.tan...@gmail.com>
> Sent: Wednesday, November 13, 2013 5:04 PM
>> Ken Tanzer <ken.tan...@gmail.com> writes:
>>>> I am not very much surprised if such a file misbehaves, because the
>>>> "format-patch | am" pipeline is designed to be used on patches that
>>>> can be transferred in plain-text e-mail safely. Long lines should
>>>> probably be OK, but mixed CRLF, CR and LF may be problematic.
>>> I'm not sure I understand this comment. format-patch seems to work
>>> fine on binary files.
>> The problematic is when you tell it to process text files, taking
>> into account various common text breakages may be introduced to the
>> payload, and line-end conversion is among the operations that the
>> user may be telling it to munge the perfectly-fine input, in an
>> attempt to compensate.
>>> Stefan Beller <stefanbel...@googlemail.com> writes:
>>>> I do have this global config
>>>> regarding line endings.
> Do you have one of these line ending conversion settings active in your
> config file?
> It sounds like the 'git am' script may be silencing the warnings too
> aggressively if that is the case.
A data system that puts you in control
100% Free Software
Subscribe to the mailing list to
learn more about AGENCY or
follow the discussion.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html