From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: philipk@posteo.net, Emacs-devel@gnu.org
Subject: Re: Amending commits
Date: Tue, 27 Sep 2022 13:37:24 +0200 [thread overview]
Message-ID: <878rm559qj.fsf@gnus.org> (raw)
In-Reply-To: <83a66mku8o.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 26 Sep 2022 18:53:11 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> A vc-checkin without anything to check in? I didn't know that that was
>> possible, and it doesn't seem like a natural work flow.
>
> It's no less natural than "git commit --amend" from the command line.
Which is pretty unnatural.
So I guess the conclusion here is that I should just go ahead and add a
vc command that does the right thing for this use case.
> How do you fix log messages today when you apply patches by others?
I use debbugs-gnu.
next prev parent reply other threads:[~2022-09-27 11:37 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
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 [this message]
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=878rm559qj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=Emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=philipk@posteo.net \
/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).