git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <stefan.naewe@atlas-elektronik.com>
To: <git@vger.kernel.org>
Subject: Bug or feature: format-patch breaks long subject lines
Date: Thu, 12 Oct 2017 08:45:19 +0000	[thread overview]
Message-ID: <3405d79e-f7be-322c-615e-fd7d8987c0cf@atlas-elektronik.com> (raw)

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

             reply	other threads:[~2017-10-12  8:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  8:45 stefan.naewe [this message]
2017-10-12 10:12 ` Bug or feature: format-patch breaks long subject lines Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3405d79e-f7be-322c-615e-fd7d8987c0cf@atlas-elektronik.com \
    --to=stefan.naewe@atlas-elektronik.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).