git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Leandro Lucarella <leandro.lucarella@sociomantic.com>
Cc: <git@vger.kernel.org>
Subject: Re: 2.10.0: git log --oneline prints gpg signatures in 4 lines
Date: Wed, 21 Sep 2016 09:19:04 -0700	[thread overview]
Message-ID: <xmqqh999b4zr.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160920170954.38b24284@labs-064.localdomain> (Leandro Lucarella's message of "Tue, 20 Sep 2016 17:09:54 +0200")

Leandro Lucarella <leandro.lucarella@sociomantic.com> writes:

> Hi, starting from 2.10.0 I noticed that when using git log --oneline,
> if commits are signed with GPG, now the signatures are printed too, and
> it takes 3 lines for the signature information + 1 line for the title
> of the commit, so suddenly --oneline became --fourline :)
>
> Is this really intended?

I think so.  The documentation for --oneline may say "one line per
commit" but in reality, some things cannot be expressed on one line.
It should probably be described as "commit object name and its log
message is formatted to be on a single line" without limiting other
things that the user may have asked to be shown.

And show-signature is an example of what the user additionally can
ask that cannot be fit on a single line.  There probably are others.





      parent reply	other threads:[~2016-09-21 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 15:09 2.10.0: git log --oneline prints gpg signatures in 4 lines Leandro Lucarella
2016-09-20 23:15 ` Jeff King
2016-09-21 10:24   ` Leandro Lucarella
2016-09-21 13:53   ` Leandro Lucarella
2016-09-21 15:05     ` Michael J Gruber
2016-09-21 16:26   ` Junio C Hamano
2016-09-21 16:19 ` Junio C Hamano [this message]

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=xmqqh999b4zr.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=leandro.lucarella@sociomantic.com \
    /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).