unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: vc-log bug?
Date: Mon, 14 Dec 2009 18:52:51 +0200	[thread overview]
Message-ID: <87vdg9lcpo.fsf@kobe.laptop> (raw)
In-Reply-To: <200912141605.nBEG56oA026171@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Mon, 14 Dec 2009 08:05:06 -0800 (PST)")

On Mon, 14 Dec 2009 08:05:06 -0800 (PST), Dan Nicolaescu <dann@ics.uci.edu> wrote:
> Giorgos Keramidas <keramida@ceid.upatras.gr> writes:
>
>   > Some of the recent VC changes broke vc-log for Mercurial here.  My HOME
>   > directory now has less than 2000 changesets:
>   >
>   >   changeset:   789:943233c01bf5
>   >   tag:         tip
>   >   user:        Giorgos Keramidas <keramida@ceid.upatras.gr>
>   >   date:        Mon Dec 14 08:49:03 2009 +0200
>   >   summary:     agenda: update clock/time table for today's work
>   >
>   > but when I type `C-x v l' the latest VC code tries to see the log of
>   > changes 2000:tip.
>
> Thanks.  This is a bug in vc-hg.el.  Fixed like this:
>
> --- vc-hg.el.~1.108.~  2009-12-07 00:53:20.000000000 -0800
> +++ vc-hg.el           2009-12-14 07:56:11.000000000 -0800
> @@ -223,7 +223,7 @@ If nil, use the value of `vc-diff-switch
>                   (repeat :tag "Argument List" :value ("") string))
>    :group 'vc-hg)
>
> -(defun vc-hg-print-log (files buffer &optional shortlog limit start-revision)
> +(defun vc-hg-print-log (files buffer &optional shortlog start-revision limit)
>    "Get change log associated with FILES."
>    ;; `vc-do-command' creates the buffer, but we need it before running
>    ;; the command.

Excellent!  I'll rebuild with this patch and let you know :)





  reply	other threads:[~2009-12-14 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 15:29 vc-log bug? Giorgos Keramidas
2009-12-14 16:05 ` Dan Nicolaescu
2009-12-14 16:52   ` Giorgos Keramidas [this message]
2009-12-14 16:54     ` Giorgos Keramidas

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=87vdg9lcpo.fsf@kobe.laptop \
    --to=keramida@ceid.upatras.gr \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.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.
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).