unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: limit the number of log entries displayed by C-x v l
Date: Thu, 12 Nov 2009 18:21:56 -0800 (PST)	[thread overview]
Message-ID: <200911130221.nAD2Lu4q007527@godzilla.ics.uci.edu> (raw)
In-Reply-To: <jwvws1vfcrh.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 12 Nov 2009 20:18:49 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

  > > Logs for some big trees can be huge, the Linux one is millions of lines.
  > 
  > Yes, this is a fairly serious problem.  We need to refine the
  > `print-log' backend op to be able to control it somehow.  E.g. in
  > vc-annotate, it'd be good to be able to get just the log message
  > corresponding to a particular commit.

With the proposed backend change that just needs
vc-annotate-show-log-revision-at-line to pass a 1 as the last argument
to vc-print-log-internal.

  > For a generic `vc-print-log' operation where the user doesn't specify
  > any particular revision, I wonder what the best UI should be.  What do
  > other front-ends (e.g. loggerhead, viewCVS, ...) do to cope with the
  > large number of log messages?

Sorry, no idea.
gitk seems to show all the entries, but it shows only the short log by default.

  > Maybe we should show just the first thousand or so by default and then
  > provide a button (and command) in log-view-mode to get more?

That could work.  
It would work with the proposed backend change.

C-x v l call would call the backend to show vc-log-show-entries, then
the button would get the revision id for the last entry in the buffer,
and it would then call the backend starting from that revision to
request more entries.




  reply	other threads:[~2009-11-13  2:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 23:19 limit the number of log entries displayed by C-x v l Dan Nicolaescu
2009-11-13  1:18 ` Stefan Monnier
2009-11-13  2:21   ` Dan Nicolaescu [this message]
2009-11-13  3:19     ` Stefan Monnier
2009-11-13  5:02       ` Dan Nicolaescu
2009-11-13 14:10         ` Stefan Monnier
2009-11-15 20:55           ` Dan Nicolaescu
2009-11-15 21:34             ` Chong Yidong
2009-11-16  9:40             ` Dan Nicolaescu
2009-11-16 14:22               ` Stefan Monnier
2009-11-16 15:10                 ` Dan Nicolaescu
2009-11-16 15:41                   ` Stefan Monnier
2009-11-16 20:40                     ` Dan Nicolaescu
2009-11-17 13:44           ` Dan Nicolaescu
2009-11-17 19:54             ` Stefan Monnier
2009-11-18 18:19               ` Dan Nicolaescu
2009-11-19  0:52                 ` Stefan Monnier
2009-11-19  7:23                   ` Thierry Volpiatto
2009-11-20  6:59                     ` Dan Nicolaescu
2009-11-20  7:19                       ` Thierry Volpiatto
2009-11-20 14:11                       ` Stefan Monnier
2009-11-20 15:26                         ` Dan Nicolaescu
2009-11-21  4:27                           ` Stephen J. Turnbull
2009-11-22 20:12                             ` Stefan Monnier
2009-11-22 23:02                               ` Štěpán Němec
2009-11-23  2:29                                 ` Stefan Monnier
2009-11-23  3:49                                   ` Bob Rogers
2009-11-23  5:17                                     ` Stefan Monnier
2009-11-22 20:10                           ` Stefan Monnier
2009-12-06 17:43                   ` Dan Nicolaescu
2009-12-07  2:12                     ` Stefan Monnier
2009-11-13  6:59     ` Giorgos Keramidas
2009-11-14 10:10 ` Alfred M. Szmidt
2009-11-14 23:29   ` Richard Stallman
2009-11-14 23:34     ` Andreas Schwab
2009-11-15 22:38       ` Richard Stallman
2009-11-15 22:52         ` Andreas Schwab
2009-11-17  7:56           ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200911130221.nAD2Lu4q007527@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).