From: Dmitry Gutov <dgutov@yandex.ru>
To: Fredrik Nyqvist <fredrik.nyqvist94@gmail.com>
Cc: 38343@debbugs.gnu.org
Subject: bug#38343: 27.0.50; vc git: Cannot edit outgoing log (like git commit --amend)
Date: Wed, 27 Nov 2019 02:10:33 +0200 [thread overview]
Message-ID: <18f1bbf5-46ad-99e5-51dc-1bd9ddfece33@yandex.ru> (raw)
In-Reply-To: <CAEhcwWZpK581rpxQeU=B9Gq8qu+gp7e41TcAtWPhK4BvvtFzxQ@mail.gmail.com>
On 26.11.2019 22:43, Fredrik Nyqvist wrote:
> Den mån 25 nov. 2019 kl 23:49 skrev Dmitry Gutov <dgutov@yandex.ru
> <mailto:dgutov@yandex.ru>>:
>
> On 25.11.2019 22:16, Fredrik Nyqvist wrote:
> > Yes, I have tried the option you mention to edit the last commit
> with
> > C-x C-e and it is working fine.
> > But It seems that it only allows amending the last commit if I have
> > edited a file.
>
> Yes. Not sure how to change an arbitrary commit in Git anyway (without
> interactive rebase). The best approximation looks like this:
>
> https://stackoverflow.com/a/48999882/615245
>
>
> I am not sure how to do it in a good way either. Maybe the option to
> edit an
> older commit message could be skipped for vc-git. And then just allow amend
> on the latest one.
The question is how to skip. Error in the end, after the user has
already written the new commit message?
Or add a backend predicate action, like "can edit revision ##". That's
one more action, though.
next prev parent reply other threads:[~2019-11-27 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 10:01 bug#38343: 27.0.50; vc git: Cannot edit outgoing log (like git commit --amend) Fredrik Nyqvist
2019-11-25 11:48 ` Dmitry Gutov
2019-11-25 20:16 ` Fredrik Nyqvist
2019-11-25 22:49 ` Dmitry Gutov
2019-11-26 20:43 ` Fredrik Nyqvist
2019-11-27 0:10 ` Dmitry Gutov [this message]
2019-11-27 20:11 ` Fredrik Nyqvist
2019-11-27 22:08 ` Dmitry Gutov
2019-11-28 20:48 ` Fredrik Nyqvist
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=18f1bbf5-46ad-99e5-51dc-1bd9ddfece33@yandex.ru \
--to=dgutov@yandex.ru \
--cc=38343@debbugs.gnu.org \
--cc=fredrik.nyqvist94@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).