From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master de76a16: Performance improvements for vc-hg
Date: Mon, 08 Feb 2016 22:21:48 +0200 [thread overview]
Message-ID: <83io1zosv7.fsf@gnu.org> (raw)
In-Reply-To: <56B8F682.7040404@dancol.org> (message from Daniel Colascione on Mon, 8 Feb 2016 12:11:46 -0800)
> From: Daniel Colascione <dancol@dancol.org>
> Date: Mon, 8 Feb 2016 12:11:46 -0800
>
> > Having to go through the trouble of re-implementing part of the VCS to
> > parse the internal data to figure out the working revision, even though
> > we have no idea if the user will ever care, is deeply unsatisfactory.
>
> I find the information useful, and we can now get it cheaply.
We are paying a non-trivial price as a project for that information,
see for example bug#21559. Maybe it should be an option, off by
default?
> Users can easily remove vc-hg from vc-handled-backends if they don't
> want the functionality.
That's hardly user-friendly, IMO.
next prev parent reply other threads:[~2016-02-08 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160208185311.9470.7389@vcs.savannah.gnu.org>
[not found] ` <E1aSqvv-0002TM-Vt@vcs.savannah.gnu.org>
2016-02-08 19:55 ` [Emacs-diffs] master de76a16: Performance improvements for vc-hg Stefan Monnier
2016-02-08 20:11 ` Daniel Colascione
2016-02-08 20:21 ` Eli Zaretskii [this message]
2016-02-08 20:28 ` Daniel Colascione
2016-02-08 21:01 ` Eli Zaretskii
2016-02-08 21:09 ` Daniel Colascione
2016-02-08 21:39 ` VC's modeline (was: [Emacs-diffs] master de76a16: Performance improvements for vc-hg) Stefan Monnier
2016-02-08 22:02 ` VC's modeline Óscar Fuentes
2016-02-09 15:15 ` Stefan Monnier
2016-02-09 17:13 ` Óscar Fuentes
2016-02-10 15:16 ` Stefan Monnier
2016-02-13 20:01 ` Dmitry Gutov
2016-02-13 9:33 ` Markus Triska
2016-02-08 23:29 ` Daniel Colascione
2016-02-13 9:35 ` Markus Triska
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=83io1zosv7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--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 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.