git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Hunter <larhun.it@gmail.com>
To: git@vger.kernel.org
Subject: [Bug] git log --show-signature print extra carriage return ^M
Date: Sun, 4 Mar 2018 18:09:25 +0100	[thread overview]
Message-ID: <CAL+2DvQZ2V9c5Tmn8KCoDOuioOiBsGJspSTVin4qw1oFO2QAwA@mail.gmail.com> (raw)

There is bug using "git log --show-signature" in my installation

    git 2.16.2.windows.1
    gpg (GnuPG) 2.2.4
    libgcrypt 1.8.2

that prints (with colors) an extra ^M (carriage return?) at the end of
the gpg lines. As an example, the output of "git log --show-signature
HEAD" looks like:

    $ git log --show-signature HEAD
    commit 46c490188ebd216f20c454ee61108e51b481844e (HEAD -> master)
    gpg: Signature made 03/04/18 16:53:06 ora solare Europa occidentale^M
    gpg:                using RSA key ...^M
    gpg: Good signature from "..." [ultimate]^M
    Author: ... <...>
    Date:   Sun Mar 4 16:53:06 2018 +0100
    ...

To help find a fix, I tested the command "git verify-commit HEAD" that
prints (without colors) the same lines without extra ^M characters.

    $ git verify-commit HEAD
    gpg: Signature made 03/04/18 16:53:06 ora solare Europa occidentale
    gpg:                using RSA key ...
    gpg: Good signature from "..." [ultimate]

Thanks,
Larry

             reply	other threads:[~2018-03-04 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 17:09 Larry Hunter [this message]
2018-03-05 14:29 ` [Bug] git log --show-signature print extra carriage return ^M Johannes Schindelin
2018-03-06  9:47   ` Larry Hunter
2018-04-28 12:18     ` Johannes Schindelin

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=CAL+2DvQZ2V9c5Tmn8KCoDOuioOiBsGJspSTVin4qw1oFO2QAwA@mail.gmail.com \
    --to=larhun.it@gmail.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.
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).