git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artur Skawina <art.08.09@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: RFC: Adding an option to log-like commands to call an external command for each revision
Date: Sun, 12 Sep 2010 00:17:15 +0200	[thread overview]
Message-ID: <4C8BFFEB.5090902@gmail.com> (raw)
In-Reply-To: <AANLkTi=WokEQMDc92SoWXPJW67dy0q79WW9RajrBHRx3@mail.gmail.com>

On 09/11/10 17:56, Ævar Arnfjörð Bjarmason wrote:
>>> I have this alias in my .gitconfig:
>>>
>>>     review = "!f() { for rev in $(git rev-list --reverse \"$@\"); do
>>> git show $rev; done; }; f"
>>>
>>> I use it after I "git pull" to see what changed, e.g.:
>>>
>>>     git review 49ea7b8..e1ef3c1

> I just like the UI of having each commit "pop up" where I can either
> page up/down within the commit, or dismiss it with "q" and go to the
> next one.

Something like

$ LESS="$LESS +/^commit " git whatchanged -p --reverse ORIG_HEAD..

will let you jump between the commits using 'n' for next, 'N' for
previous.

Not 100% the same, i know, but much faster than your solution.
(mostly because of pipelining; while you're reviewing one change
the next commits are already being prepared. For deep, but filtered
queries, i often do it more explicitly as "git..|bag|less +/^commit"
to avoid the stalls.)

artur

  parent reply	other threads:[~2010-09-11 22:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29 20:30 RFC: Adding an option to log-like commands to call an external command for each revision Ævar Arnfjörð Bjarmason
2010-08-29 20:39 ` Jonathan Nieder
2010-08-30  3:08 ` Jeff King
2010-09-11 15:56   ` Ævar Arnfjörð Bjarmason
2010-09-11 17:09     ` Mark Lodato
2010-09-11 19:07     ` Ævar Arnfjörð Bjarmason
2010-09-11 22:17     ` Artur Skawina [this message]
2010-09-12 21:25     ` Junio C Hamano
2010-09-12 22:44       ` Ævar Arnfjörð Bjarmason

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=4C8BFFEB.5090902@gmail.com \
    --to=art.08.09@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).