From 93e9a3736be6853c0f1c6fac8e9e697eecdff4e4 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Thu, 17 Oct 2024 21:14:45 +0800 Subject: [PATCH] ; * lisp/vc/vc.el: Drop some old notes Firstly, we are unlikely to do any unifying, because both amend capabilities have been around for a long time now and we don't want to break people's usage. Secondly, there is now a plan for dealing with dangerous git operations described in bug#64055. (cherry picked from commit 38071e39892fe0270f91746bd5f55c056cb00921) --- lisp/vc/vc.el | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/lisp/vc/vc.el b/lisp/vc/vc.el index 8a27e89983d..c72bbabc859 100644 --- a/lisp/vc/vc.el +++ b/lisp/vc/vc.el @@ -704,22 +704,6 @@ ;; ;; - Add the ability to list tags and branches. ;; -;;;; Unify two different versions of the amend capability -;; -;; - Some back ends (SCCS/RCS/SVN/SRC), have an amend capability that can -;; be invoked from log-view. -;; -;; - The git backend supports amending, but in a different -;; way (press `C-c C-e' in log-edit buffer, when making a new commit). -;; -;; - Doing message editing in log-view might be a natural way to go -;; about it, but editing any but the last commit (and even it, if it's -;; been pushed) is a dangerous operation in Git, which we shouldn't make -;; too easy for users to perform. -;; -;; There should be a check that the given comment is not reachable -;; from any of the "remote" refs? -;; ;;;; Other ;; ;; - asynchronous checkin and commit, so you can keep working in other -- 2.39.5