unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,  philipk@posteo.net,  Emacs-devel@gnu.org
Subject: Re: Amending commits
Date: Tue, 27 Sep 2022 15:04:20 -0700	[thread overview]
Message-ID: <87leq4bhjv.fsf@melete.silentflame.com> (raw)
In-Reply-To: <871qrw3i6u.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 27 Sep 2022 18:17:45 +0200")

Hello,

On Tue 27 Sep 2022 at 06:17PM +02, Lars Ingebrigtsen wrote:

> Sean Whitton <spwhitton@spwhitton.name> writes:
>
>> Couldn't it do a rebase to reword the old commit?  I often do 'git
>> rebase -i' only for the purpose of rewording an unpushed, non-tip
>> commit, and it would be nice for that to be automated (eventually!).
>
> That should be possible (or un-checkin and then stash commits and
> reapply), but sounds like major work.

Right.  If you're planning on working on the 'commit --amend' part,
could you add an error specifically stating that amending the messages
of older commits is not yet {supported|implemented}, please?  Currently
I think you just get a Lisp error or maybe nothing happens at all.
Given that I do this a lot I'll probably look into the rest of it at
some point.

-- 
Sean Whitton



  reply	other threads:[~2022-09-27 22:04 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
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 [this message]
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=87leq4bhjv.fsf@melete.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=Emacs-devel@gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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).