From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: git show
Date: Fri, 01 Nov 2019 11:57:43 -0400 [thread overview]
Message-ID: <jwvbltvtwxm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87eeyr3d4m.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 01 Nov 2019 15:06:01 +0100")
> It's not very convenient -- if the commit is old, I have to hit either
> "Show 2X entries" or "Show unlimited entries", which are slow.
It's worse: if the commit is not in the current branch it won't be
listed at all, and `C-x v L` doesn't let you show the log corresponding
to another branch.
If `C-x v l` accepted a C-u to specify the "revision" for which to show
the log, then it would solve both problems: you could get the log
of other branches and you could see the commit message and the diff of
a specific REVision with:
C-u C-x v l <REV> RET
followed by hitting `D` on the first element to see the diff
-- Stefan
next prev parent reply other threads:[~2019-11-01 15:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 13:51 git show Lars Ingebrigtsen
2019-11-01 14:01 ` Eli Zaretskii
2019-11-01 14:06 ` Lars Ingebrigtsen
2019-11-01 15:57 ` Stefan Monnier [this message]
2019-11-02 8:01 ` Steinar Bang
2019-11-02 11:00 ` Dmitry Gutov
2019-11-02 18:45 ` Juri Linkov
2019-11-03 14:32 ` Lars Ingebrigtsen
2019-11-04 22:37 ` Steinar Bang
2019-11-04 22:48 ` Steinar Bang
2019-11-05 7:02 ` Steinar Bang
2019-11-05 16:33 ` Óscar Fuentes
2019-11-02 18:48 ` dired-vc-rename (was: git show) Juri Linkov
2019-11-03 14:33 ` dired-vc-rename Lars Ingebrigtsen
2019-11-02 14:29 ` git show Lars Ingebrigtsen
2019-11-02 18:16 ` Stefan Monnier
2019-11-03 15:11 ` Lars Ingebrigtsen
[not found] ` <dc6ccd02-c637-f8ca-c025-7860421809af@yandex.ru>
[not found] ` <87imo33ddk.fsf@gnus.org>
2019-11-01 14:17 ` Dmitry Gutov
2019-11-01 15:35 ` Lars Ingebrigtsen
2019-11-02 18:42 ` Juri Linkov
2019-11-02 18:59 ` Eli Zaretskii
2019-11-02 19:09 ` Stephen Berman
2019-11-02 21:33 ` Juri Linkov
2019-11-02 22:06 ` Juri Linkov
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=jwvbltvtwxm.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).