unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 26 Nov 2019 00:49:18 +0200	[thread overview]
Message-ID: <e16cb4ab-3c93-66c5-a9a7-482ce38e7d2c@yandex.ru> (raw)
In-Reply-To: <CAEhcwWaSxg=jJR54+16tB3EDDKF3CoeKhc9TKLyOu1v6oJa6=A@mail.gmail.com>

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

> As I understand it I need to edit a file and then do vc-next-action to 
> get to the log-edit buffer
> where you can do C-x C-e.

Yes.

> I could not find a way to do this if just the commit message is supposed 
> to be updated.

And that is indeed the main downside of our current solution.

(The way to do it is to edit, call vc-next-action, then undo the edit in 
the file, but commit the amended message anyway. Which could be more 
efficient).





  reply	other threads:[~2019-11-25 22:49 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 [this message]
2019-11-26 20:43       ` Fredrik Nyqvist
2019-11-27  0:10         ` Dmitry Gutov
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=e16cb4ab-3c93-66c5-a9a7-482ce38e7d2c@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).