# Bug or feature: format-patch breaks long subject lines

2 messages from 2017-10-12 to 2017-10-12. Participants: stefan.naewe@atlas-elektronik.com, Junio C Hamano.
Thread: https://gitlist.dev/t/46955

## stefan.naewe@atlas-elektronik.com, 2017-10-12 08:45

Subject: Bug or feature: format-patch breaks long subject lines
Message-ID: <3405d79e-f7be-322c-615e-fd7d8987c0cf@atlas-elektronik.com>
URL: https://gitlist.dev/e/3405d79e-f7be-322c-615e-fd7d8987c0cf%40atlas-elektronik.com

```
Hello list,

git format-patch breaks (or better: word-wraps) long subject lines.

This is on Windows 7 with

$ git --version
git version 2.14.2.windows.2

Reproduce with (some output omitted):

------------------------------------------------------------------------------
$ git init test-format-patch
$ cd test-format-patch
$ touch file
$ git add file
$ git commit -m"0123456789012345678901234567890123456789012345678901234567890123456789"
$ git format-patch -1 --stdout
From ec711cca330f1032d286114932a90488542f1da2 Mon Sep 17 00:00:00 2001
From: Stefan Naewe <stefan.naewe@gmail.com>
Date: Thu, 12 Oct 2017 10:36:52 +0200
Subject: [PATCH]
 0123456789012345678901234567890123456789012345678901234567890123456789

---
 file | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 file

diff --git a/file b/file
new file mode 100644
index 0000000..e69de29
--
2.14.2.windows.2
------------------------------------------------------------------------------

Is this the expected behaviour?

Thanks,
  Stefan
-- 
----------------------------------------------------------------
/dev/random says: I Have To Stop Now, My Fingers Are Getting Hoarse!
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')" 
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9  9666 829B 49C5 9221 27AF
```

## Junio C Hamano, 2017-10-12 10:12

Subject: Re: Bug or feature: format-patch breaks long subject lines
Message-ID: <xmqqfuaoznby.fsf@gitster.mtv.corp.google.com>
URL: https://gitlist.dev/e/xmqqfuaoznby.fsf%40gitster.mtv.corp.google.com
In-Reply-To: <3405d79e-f7be-322c-615e-fd7d8987c0cf@atlas-elektronik.com>

```
<stefan.naewe@atlas-elektronik.com> writes:

> Is this the expected behaviour?

Yes, it is expected.  Your are seeing the header folding in play.
"mailinfo" (hence "am") will grok it just fine, I think.

```