unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: C-x v g going further back in time?
Date: Mon, 26 Jan 2004 14:28:00 GMT	[thread overview]
Message-ID: <jwvisiybxhj.fsf-monnier+gnu.emacs.help@asado.iro.umontreal.ca> (raw)
In-Reply-To: wc3brorczn8.fsf@mu.cis.ohio-state.edu

> 1) the *vc* buffer is used both for 'C-x v l' and also when you do
>    'C-x v v' to commit a file, so it might contain either info that

It can also be used for another file.  I think we just need to add
a variable that stores the "it's a log" info, along the one that stores the
file's name.

> 2) cache coherency problem.  What if the log info is updated b/c of
>    new commits?  Do you always want the outdated log info?

I wouldn't worry too much about it.  If the commits are done via VC,
they'll overwrite the *vc* buffer so it's safe.  And even if it somehow
does not happen, it's rather unlikely that the user will be bothered by the
lack of some brand new commits: when using vc-annotate you're typically
looking at past changes.  And you can always add a `revert-buffer-function'
such that the user can refresh explicitly the log info.


        Stefan

  reply	other threads:[~2004-01-26 14:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 21:45 C-x v g going further back in time? Benjamin Rutt
2004-01-08 22:14 ` Andrew Taylor
2004-01-08 22:16 ` Benjamin Rutt
2004-01-08 22:47   ` Stefan Monnier
2004-01-21  1:02     ` Benjamin Rutt
2004-01-21  3:18       ` Stefan Monnier
2004-01-26  0:38         ` Benjamin Rutt
2004-01-26 14:28           ` Stefan Monnier [this message]
2004-01-26 15:03             ` Benjamin Rutt
2004-01-26 16:44               ` Stefan Monnier
2004-01-26 18:33               ` Stefan Monnier
2004-01-12  2:55   ` Benjamin Rutt

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=jwvisiybxhj.fsf-monnier+gnu.emacs.help@asado.iro.umontreal.ca \
    --to=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.
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).