git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Cc: Kevin <compufreak@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: How to get status-like short format for old commits?
Date: Mon, 26 Mar 2012 16:14:56 -0400	[thread overview]
Message-ID: <20120326201456.GC13098@sigill.intra.peff.net> (raw)
In-Reply-To: <CAA01CsppeF8r_hDhuE7snExxJ6zaWdt5Znu82ZzDmyNMzWRDfA@mail.gmail.com>

On Mon, Mar 26, 2012 at 08:53:45PM +0200, Piotr Krukowiecki wrote:

> [log --name-status]
> not so nice as status, but still ok.

Yeah, the code to print the verbose "modified: foo.c" style is specific
to status. We could refactor it to be a new generic diff output type,
which would not be that hard. In practice, though, I think people choose
either "--stat --summary" if they want to show to a person (it's a
superset of what status shows, because it also contains the number of
lines changed for each file), or "--raw" if they need something
machine-readable.

Does one of those work for you? If not, it might be a fun and relatively
simple exercise to create a --verbose-name-status that looks like the
output of "git status" (you could also do it by post-processing
--name-status output, but that is less fun and more hacky :) ).

-Peff

      reply	other threads:[~2012-03-26 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 11:24 How to get status-like short format for old commits? Piotr Krukowiecki
2012-03-26 12:07 ` Kevin
2012-03-26 18:53   ` Piotr Krukowiecki
2012-03-26 20:14     ` Jeff King [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=20120326201456.GC13098@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=compufreak@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=piotr.krukowiecki@gmail.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).