From: Akib Azmain Turja <akib@disroot.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Package Eat on NonGNU ELPA diverged
Date: Tue, 29 Nov 2022 02:36:16 +0600 [thread overview]
Message-ID: <87bkoq6clb.fsf@disroot.org> (raw)
In-Reply-To: <875yeyesoj.fsf@posteo.net> (Philip Kaludercic's message of "Mon, 28 Nov 2022 20:21:32 +0000")
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
Philip Kaludercic <philipk@posteo.net> writes:
> Akib Azmain Turja <akib@disroot.org> writes:
>
>> I mistakenly wrote a commit message with a lot of mistakes, and
>> unfortunately I also pushed it immediately. After some 10-20 minutes,
>> I noticed the thing and quickly fixed that commit message (but not the
>> files) and force pushed it. But within that 10-20 minutes, ELPA
>> machinery fetch from my repository, and now the two repositories
>> diverged.
>>
>> Is there any chance to do something on ELPA side, or do I have to do
>> something on my side?
>
> IIRC You could add the ELPA mirror as a remote, then merge the diverged
> branch onto your own and push that.
Does that mean that there is really nothing doable on a server-side? I
wish there was something.
Anyway, I'll merge if the above is true.
--
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-11-28 20:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 19:49 Package Eat on NonGNU ELPA diverged Akib Azmain Turja
2022-11-28 20:21 ` Philip Kaludercic
2022-11-28 20:36 ` Akib Azmain Turja [this message]
2022-11-28 21:02 ` Stefan Monnier
2022-11-29 7:59 ` Akib Azmain Turja
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=87bkoq6clb.fsf@disroot.org \
--to=akib@disroot.org \
--cc=emacs-devel@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 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.