all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 6399@debbugs.gnu.org
Subject: bug#6399: Confirm vc commits when the files do not match those marked in vc-dir
Date: Sun, 18 Jul 2021 15:10:45 +0200	[thread overview]
Message-ID: <87wnpnrcmi.fsf@gnus.org> (raw)
In-Reply-To: <jn8w6mz0qn.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 10 Jun 2010 23:50:24 -0400")

Glenn Morris <rgm@gnu.org> writes:

> I've made this mistake a few times now:
>
> 1) Mark say 5 files in vc-dir.
>
> 2) Press v to get a vc-log buffer.
>
> 3) Realize I should not have marked one of the 5 files, and unmark it
> in the vc-dir buffer.
>
> 4) Forget to kill the existing vc-log buffer, and so end up committing
> all 5 files anyway.

Somehow that has never happened to me, so I guess it's never occurred to
me to do something like that.  But I see that the problem is still
present in Emacs 28.

> I wish that at step 4 when I try to commit, Emacs would check if the
> files about to be commited match those marked in the vc-dir buffer,
> and if not ask me to confirm the commit.

Yeah, that seems like a good idea.  I can't really imagine somebody
altering the marked files in the vc-dir buffer without wanting to affect
which files get checked in on the `C-c C-c'.  But before I start poking
at this -- would adding a query like this disrupt somebody's work flow?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-07-18 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11  3:50 bug#6399: Confirm vc commits when the files do not match those marked in vc-dir Glenn Morris
2010-06-11  5:53 ` Stefan Monnier
2021-07-18 13:10 ` Lars Ingebrigtsen [this message]

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=87wnpnrcmi.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=6399@debbugs.gnu.org \
    --cc=rgm@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 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.