git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Jean-Baptiste Quenot <jbq@caraldi.com>
Cc: git@vger.kernel.org
Subject: Re: [tig] Feeding specific revisions to tig
Date: Wed, 4 Jun 2008 19:08:58 -0400	[thread overview]
Message-ID: <20080604230858.GA27136@sigill.intra.peff.net> (raw)
In-Reply-To: <ae63f8b50806041304i20de789ej492681f4b9306934@mail.gmail.com>

On Wed, Jun 04, 2008 at 10:04:45PM +0200, Jean-Baptiste Quenot wrote:

> 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.

Ah. Adding "-F" probably wouldn't be that much work, but tig spawns "git
log" internally, so you would probably end up with the same problem
there. Converting tig to use "git rev-list --stdin" would fix that, but
is probably a bit of major surgery.

-Peff

  reply	other threads:[~2008-06-04 23:10 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
2008-06-04 23:08     ` Jeff King [this message]
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=20080604230858.GA27136@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=jbq@caraldi.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).