From: "Jean-Baptiste Quenot" <jbq@caraldi.com>
To: git@vger.kernel.org
Subject: Re: [tig] Feeding specific revisions to tig
Date: Wed, 4 Jun 2008 22:04:45 +0200 [thread overview]
Message-ID: <ae63f8b50806041304i20de789ej492681f4b9306934@mail.gmail.com> (raw)
In-Reply-To: <20080604192916.GB17327@sigill.intra.peff.net>
2008/6/4 Jeff King <peff@peff.net>:
> On Wed, Jun 04, 2008 at 08:52:14PM +0200, Jean-Baptiste Quenot wrote:
>
>> Ideally I'd like to feed this list of commits to tig, so that I can
>> watch the commit diff and summary easily and switch from one commit to
>> another. But tig only behaves as a pager, and does not help for this.
>
> I think there are two issues here, but both are solvable:
>
> 1. You want to see _just_ these commits, but not the whole ancestry
> chain. In that case, you want to use --no-walk. E.g.:
>
> tig --no-walk commit1 commit2 ...
>
> Though it seems there are a few display artifacts. If I do
>
> tig --no-walk tig-0.1 tig-0.2
>
> I get the 2 commits I expect, but also two "extra" blank
> commits at the bottom.
I confirm there are extra blank lines at the bottom. As many as real
commit lines.
> 2. tig works like a pager when stdin is not a tty. You can work
> around this by using xargs to give the commits to it on the
> command line, and then redirect stdin from the tty.
>
> ... | xargs sh -c 'tig --no-walk "$@" </dev/tty'
Thanks for the suggestion. However, my list of commits is too long,
the shell errors out with "tig: command too long". I'd like to feed
tig with a list of commits from stdin, or from a file.
Something like: ... | tig --no-walk -F -
Which means: take the list of revisions from specified file, or here -
for stdin, a la grep.
Cheers,
--
Jean-Baptiste Quenot
http://jbq.caraldi.com/
next prev parent reply other threads:[~2008-06-04 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 18:52 [tig] Feeding specific revisions to tig Jean-Baptiste Quenot
2008-06-04 19:29 ` Jeff King
2008-06-04 20:04 ` Jean-Baptiste Quenot [this message]
2008-06-04 23:08 ` Jeff King
2008-08-06 11:06 ` Jonas Fonseca
2008-08-08 21:19 ` Jeff King
2008-08-10 9:16 ` Jonas Fonseca
2009-04-23 14:55 ` Jean-Baptiste Quenot
2009-04-27 10:21 ` Jonas Fonseca
2009-04-28 8:15 ` Jean-Baptiste Quenot
2011-09-15 15:10 ` Jean-Baptiste Quenot
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=ae63f8b50806041304i20de789ej492681f4b9306934@mail.gmail.com \
--to=jbq@caraldi.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).