From: Max Filenko <contact@filenko.ms>
To: git@vger.kernel.org
Subject: git-am drops colons in the beginning of a subject line
Date: Tue, 12 Feb 2019 12:38:25 +0100 [thread overview]
Message-ID: <m2lg2lxmmm.fsf@bouncer.i-did-not-set--mail-host-address--so-tickle-me> (raw)
Hey there,
git-am seems to omit colons in the beginning of a subject line.
I have the following simple patch (just an example):
$ cat 0001-four-colons-prepended.patch
From e8213a2d10a61c9dc75521d88d656b8d5330e6bb Mon Sep 17 00:00:00 2001
From: Max Filenko <contact@filenko.ms>
Date: Tue, 12 Feb 2019 12:21:21 +0100
Subject: [PATCH] :::: four colons prepended
---
file.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/file.txt b/file.txt
index 4dd1ef7..b5da95d 100644
--- a/file.txt
+++ b/file.txt
@@ -1 +1 @@
-This is a file.
+This is a plain text file.
--
2.17.2 (Apple Git-113)
I apply this patch:
$ git am 0001-four-colons-prepended.patch
Applying: four colons prepended
As you might have already noticed git message above doesn't have colons.
Let's double check this:
$ git show
commit 6341a6a2872f850ecb376c268b1b3bae54a6a74f (HEAD -> master)
Author: Max Filenko <contact@filenko.ms>
Date: Tue Feb 12 12:21:21 2019 +0100
four colons prepended
diff --git a/file.txt b/file.txt
index 4dd1ef7..b5da95d 100644
--- a/file.txt
+++ b/file.txt
@@ -1 +1 @@
-This is a file.
+This is a plain text file.
The commit message reads 'four colons prepended' while it should read
':::: four colons prepended'.
Colons are missing in the commit message after apllying this patch.
I don't think that's an expected behaviour, isn't it?
--
Cheers,
Max
next reply other threads:[~2019-02-12 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 11:38 Max Filenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-12 12:09 git-am drops colons in the beginning of a subject line Max Filenko
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=m2lg2lxmmm.fsf@bouncer.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact@filenko.ms \
--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).