From: Glenn Morris <rgm@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: 16902@debbugs.gnu.org
Subject: bug#16902: 24.3.50; why vc-revert keeps its diff-buffer around?
Date: Fri, 28 Feb 2014 14:53:06 -0500 [thread overview]
Message-ID: <wu61nz2evx.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m11tyncu27.fsf@gmail.com> (Leo Liu's message of "Fri, 28 Feb 2014 20:15:12 +0800")
How about extending the option vc-revert-show-diff to allow a new value,
`kill', which means to kill the diff buffer afterwards?
next prev parent reply other threads:[~2014-02-28 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 5:08 bug#16902: 24.3.50; why vc-revert keeps its diff-buffer around? Leo Liu
2014-02-28 7:17 ` Glenn Morris
2014-02-28 12:15 ` Leo Liu
2014-02-28 19:53 ` Glenn Morris [this message]
2014-02-28 21:04 ` Leo Liu
2021-09-04 9:12 ` Lars Ingebrigtsen
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=wu61nz2evx.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=16902@debbugs.gnu.org \
--cc=sdl.web@gmail.com \
/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).