all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Dmitry Gutov <dgutov@yandex.ru>, Visuwesh <visuweshm@gmail.com>,
	 Philip Kaludercic <philipk@posteo.net>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	 emacs-devel@gnu.org
Subject: Re: Amending commits
Date: Mon, 26 Sep 2022 07:53:30 +0000	[thread overview]
Message-ID: <0f4ca4f331dd30be2e0f@heytings.org> (raw)
In-Reply-To: <jwvr0zzgkih.fsf-monnier+emacs@gnu.org>


>> Yes, I said "by default": force pushes are disabled in the default 
>> settings of Git repositories, unless they have been enabled you cannot 
>> do that.
>
> Not sure if this default has changed, but last time I checked the 
> default was to allow such force pushes (`emacs.git` and `elpa.git` have 
> explicitly changed this setting to disallow them). You just need to 
> specify the `--force` option when you push.
>

These repositories have been created with git init --shared, which 
automatically sets denyNonFastforwards to true.  This has been the default 
since Git 1.5 in 2007.

>
> For those repositories like `emacs.git`, `--force` doesn't override the 
> server's wish, but you can still force push by first deleting the branch 
> and then pushing the new history.
>

With branches, yes, but not with master, unless denyDeleteCurrent has been 
set to warn or ignore.  And this is not always possible, even with 
branches: all deletions can be disallowed by setting receive.denyDeletes 
to true.



  reply	other threads:[~2022-09-26  7:53 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
2022-09-25 20:46             ` Gregory Heytings
2022-09-25 22:26               ` Stefan Monnier
2022-09-26  7:53                 ` Gregory Heytings [this message]
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=0f4ca4f331dd30be2e0f@heytings.org \
    --to=gregory@heytings.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.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 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.