all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Gregory Heytings <gregory@heytings.org>
Cc: Visuwesh <visuweshm@gmail.com>,
	 Philip Kaludercic <philipk@posteo.net>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	 emacs-devel@gnu.org
Subject: Re: Amending commits
Date: Sun, 25 Sep 2022 15:26:39 -0400	[thread overview]
Message-ID: <jwvedvzi7gw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <7a1185d7c76d3e55bc78@heytings.org> (Gregory Heytings's message of "Sun, 25 Sep 2022 18:04:18 +0000")

>> As someone who does not really understand Git, does this mean we are
>> rewriting the log message without also committing a change?  I thought
>> that was not allowed by Git.
> git commit --amend is mainly used to change a commit before pushing
> it.  Rewriting history (i.e. changing an already public commit) is (by
> default) not possible.

When people say that in Git you cannot rewrite history, what it means is
that you can't change anything about a given *commit id* (aka
"revision").
Of course, you can create a new revision (i.e. a different commit id)
with any content you like.  Things like `rebase` and `filter-repo` are
more general version of `commit --amend` and work in the same way, by
writing a whole new history.


        Stefan




  reply	other threads:[~2022-09-25 19:26 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvedvzi7gw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.org \
    --cc=philipk@posteo.net \
    --cc=visuweshm@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.