all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Tom Tromey <tromey@redhat.com>
Cc: 4497@emacsbugs.donarmstrong.com
Subject: bug#4497: 23.1; vc-print-log -vs- very long log files
Date: Wed, 18 Nov 2009 11:56:09 -0800 (PST)	[thread overview]
Message-ID: <200911181956.nAIJu9SH010417@godzilla.ics.uci.edu> (raw)
In-Reply-To: <m3eiq15ty8.fsf@fleche.redhat.com> (Tom Tromey's message of "Sun,  20 Sep 2009 12:53:19 -0600")

Tom Tromey <tromey@redhat.com> writes:

  > Please write in English if possible, because the Emacs maintainers
  > usually do not have translators to read other languages for them.
  > 
  > Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
  > and to the gnu.emacs.bug news group.
  > 
  > Please describe exactly what actions triggered the bug
  > and the precise symptoms of the bug:
  > 
  > 
  > I invoked vc-print-log from vc-dir on the emacs git repository.
  > This generates an extremely large amount of data.
  > I couldn't find a way to interrupt the log generation; I ended up
  > killing git directly from the shell.
  > 
  > It would be nice if VC were smarter about limiting the amount of log
  > output.  I am not sure exactly how I would want this to work, but at
  > least by default I probably don't want more than a couple megabytes of
  > output.

The generic part of this is solved now, there's a limit on the number of
log entries displayed by default.

But vc-git.el does not no support this feature.
When passed a non-nil LIMIT argument `vc-git-print-log' should tell "git log" 
to limit the output.





  reply	other threads:[~2009-11-18 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200912101945.nBAJjwjj014727@godzilla.ics.uci.edu>
2009-09-20 18:53 ` bug#4497: 23.1; vc-print-log -vs- very long log files Tom Tromey
2009-11-18 19:56   ` Dan Nicolaescu [this message]
2009-12-10 19:50   ` bug#4497: marked as done (23.1; vc-print-log -vs- very long log files) Emacs bug Tracking System

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=200911181956.nAIJu9SH010417@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=4497@emacsbugs.donarmstrong.com \
    --cc=tromey@redhat.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.