From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Emacs-devel@gnu.org" <Emacs-devel@gnu.org>
Subject: Re: Amending commits
Date: Sun, 25 Sep 2022 10:50:30 +0000 [thread overview]
Message-ID: <877d1ru3rd.fsf@posteo.net> (raw)
In-Reply-To: <87h70vbw2f.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 25 Sep 2022 12:14:00 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I vaguely remembered that commands for amending commits had been added,
> but I have no idea how those are supposed to be used. I searched for
> "amend" in maintaining.texi and found nothing. I found
> `vc-git-log-edit-toggle-amend', but... how is that supposed to be used?
I think that command assumed you have changes that you wish to add to
the last commit (so you couldn't just use it to reword a commit). You
start preparing a new commit using `vc-next-action', then when the
buffer appears you M-x vc-git-log-edit-toggle-amend to indicate that
this commit will be amending the previous one. So the commit message
gets replaced by that of the previous message. The rest just involves
finishing up like any other commit.
> There should be a command in `vc-dir-mode' that allows you to amend the
> last commit, I think.
That would be good, because it would also allow easier to reword a
commit that doesn't require any code changes.
next prev parent reply other threads:[~2022-09-25 10:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 10:14 Amending commits Lars Ingebrigtsen
2022-09-25 10:50 ` Philip Kaludercic [this message]
2022-09-25 11:39 ` Lars Ingebrigtsen
2022-09-25 13:58 ` Eli Zaretskii
2022-09-26 10:42 ` Lars Ingebrigtsen
2022-09-26 11:38 ` Eli Zaretskii
2022-09-26 12:00 ` Lars Ingebrigtsen
2022-09-26 15:53 ` Eli Zaretskii
2022-09-27 11:37 ` Lars Ingebrigtsen
2022-09-27 11:54 ` Eli Zaretskii
2022-09-27 12:00 ` Lars Ingebrigtsen
2022-09-27 14:01 ` Robert Pluim
2022-09-27 15:35 ` Sean Whitton
2022-09-27 15:40 ` Lars Ingebrigtsen
2022-09-27 16:10 ` Sean Whitton
2022-09-27 16:17 ` Lars Ingebrigtsen
2022-09-27 22:04 ` Sean Whitton
2022-09-28 10:57 ` Lars Ingebrigtsen
2022-09-27 16:15 ` Gregory Heytings
2022-09-28 18:09 ` Juri Linkov
2022-09-28 20:42 ` Sean Whitton
2022-09-26 14:35 ` Rudolf Schlatte
2022-09-25 11:46 ` Visuwesh
2022-09-25 12:49 ` Philip Kaludercic
2022-09-25 13:19 ` Andreas Schwab
2022-09-25 13:49 ` Philip Kaludercic
2022-09-25 16:56 ` Manuel Giraud
2022-09-25 18:04 ` Gregory Heytings
2022-09-25 19:26 ` Stefan Monnier
2022-09-25 20:15 ` Gregory Heytings
2022-09-25 20:37 ` Dmitry Gutov
2022-09-25 20:46 ` Gregory Heytings
2022-09-25 22:26 ` Stefan Monnier
2022-09-26 7:53 ` Gregory Heytings
2022-09-26 8:15 ` Andreas Schwab
2022-09-26 8:23 ` Gregory Heytings
2022-09-26 8:29 ` Andreas Schwab
2022-09-26 8:39 ` Gregory Heytings
2022-09-26 8:49 ` Andreas Schwab
2022-09-26 9:16 ` Gregory Heytings
2022-09-26 9:26 ` Andreas Schwab
2022-09-26 10:22 ` Gregory Heytings
2022-09-25 20:17 ` Alan Mackenzie
2022-09-26 10:43 ` 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=877d1ru3rd.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=Emacs-devel@gnu.org \
--cc=larsi@gnus.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 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).