git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Runge <oliver.runge@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: rev-list pretty format behavior
Date: Wed, 8 Apr 2015 19:12:05 +0200	[thread overview]
Message-ID: <CAHaCNWKYY_5JvuAk76wnrTTBaBQM2Fv8hz37tEYC5Jzm1tY-RQ@mail.gmail.com> (raw)
In-Reply-To: <5523E175.2060607@drmicha.warpmail.net>

Heyup, Dr. Gruber.

On 7 April 2015 at 15:53, Michael J Gruber <git@drmicha.warpmail.net> wrote:
> I'm wondering what the difference is - or should be - between "git log"
> and "git rev-list" with (completely) user specified output. That
> question goes both ways:
>
> - Why do we need "rev-list" to have completely flexible output when we
> have "log" with such flexibility?
>
> - Why do we even have pretty formats for "rev-list"?
>
> I'm thinking of rev-list as a raw (plumbing) revision lister much like
> cat-file is the inspection tool for the objects, and log as the human
> facing output with appropriate defaults (resp. show).
>
> Note that "rev-list -v" isn't even documented afaics.

I can't answer your questions, because I don't have a very deep
understanding of either command, but according to the "log" docu,
formating really belongs to "rev-list" and "log" only adds the diff-*
features:
------------------------------------------
The command takes options applicable to the git rev-list command
to control what is shown and how, and options applicable to the
git diff-* commands to control how the changes each commit
introduces are shown.
------------------------------------------

I also feel that perhaps "pretty" is a bit of a misnomer and naturally
is associated with "human readable", but the formating is vital for
any raw output that scripts can process.

Oliver

      reply	other threads:[~2015-04-08 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04 23:27 rev-list pretty format behavior Oliver Runge
2015-04-05 21:12 ` Junio C Hamano
2015-04-06 11:05   ` Oliver Runge
2015-04-07 13:53     ` Michael J Gruber
2015-04-08 17:12       ` Oliver Runge [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

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

  git send-email \
    --in-reply-to=CAHaCNWKYY_5JvuAk76wnrTTBaBQM2Fv8hz37tEYC5Jzm1tY-RQ@mail.gmail.com \
    --to=oliver.runge@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).