From: "Daniel Colascione" <dancol@dancol.org>
To: "Dmitry Gutov" <dgutov@yandex.ru>
Cc: 38387@debbugs.gnu.org, Andrii Kolomoiets <andreyk.mad@gmail.com>
Subject: bug#38387: 27.0.50; [PATCH] vc-hg: use 'hg summary' to populate vc-dir headers
Date: Wed, 27 Nov 2019 10:53:10 -0800 [thread overview]
Message-ID: <0366bc0bf7f7c65bdc5e869397d4c945.squirrel@dancol.org> (raw)
In-Reply-To: <7505dd70-86c1-9576-5dc9-42b1abca519e@yandex.ru>
> Hi Andrii,
>
> On 26.11.2019 17:16, Andrii Kolomoiets wrote:
>
>> By invoking single 'summary' command we can get more info about
>> repository state: parent revisions, current branch, tags, bookmarks,
>> commit status, available updates and phase.
>
> I guess the questions are:
>
> - Is this output better than the previous one? Hopefully others will
> chime in, e.g. Daniel, who wrote some major improvements to vc-hg a few
> years ago.
>
> - Is 'hg summary' stable enough? Maybe a few years from now Mercurial
> changes its output and this code stops working in all Emacs we'd have
> released in the meantime? This is why we try to use "porcelain" level
> commands (in Git terminology) when possible, not user-level.
>
What's the performance of summary like these days?
next prev parent reply other threads:[~2019-11-27 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 15:16 bug#38387: 27.0.50; [PATCH] vc-hg: use 'hg summary' to populate vc-dir headers Andrii Kolomoiets
2019-11-27 12:30 ` Dmitry Gutov
2019-11-27 13:37 ` Andreas Schwab
2019-11-27 13:56 ` Dmitry Gutov
2019-11-27 18:53 ` Daniel Colascione [this message]
2019-11-28 8:07 ` Andrii Kolomoiets
2019-12-02 0:31 ` Dmitry Gutov
2019-12-02 0:53 ` Daniel Colascione
2020-08-09 12:36 ` Lars Ingebrigtsen
2019-11-28 9:50 ` Dmitry Gutov
2019-11-28 8:20 ` Andrii Kolomoiets
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=0366bc0bf7f7c65bdc5e869397d4c945.squirrel@dancol.org \
--to=dancol@dancol.org \
--cc=38387@debbugs.gnu.org \
--cc=andreyk.mad@gmail.com \
--cc=dgutov@yandex.ru \
/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).