unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Gregory Heytings <gregory@heytings.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
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 23:37:01 +0300	[thread overview]
Message-ID: <dceb7f6e-3069-79af-4460-2d62b265baa5@yandex.ru> (raw)
In-Reply-To: <7a1185d7c7cd09d9c277@heytings.org>

On 25.09.2022 23:15, Gregory Heytings wrote:
> 
>>>> 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").
>>
> 
> Hmm... no, AFAIU, it means that (by default) you cannot replace the 
> commit history of a public repository with commits which do not have the 
> HEAD of the public repository as their parent.  E.g. if your public 
> repository is
> 
> A - B - C - D
>              ^ HEAD
> 
> you cannot change it into
> 
>      B - C - D
>    /
> A - E - F - G
>              ^ HEAD

You can even do that (if 'force pushes' are not disabled in the 
repository's settings).

It's just usually a bad idea.

So you can rewrite history, but commits are "immutable".



  reply	other threads:[~2022-09-25 20: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
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 [this message]
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=dceb7f6e-3069-79af-4460-2d62b265baa5@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --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 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).