unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja <akib@disroot.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Package Eat on NonGNU ELPA diverged
Date: Tue, 29 Nov 2022 13:59:48 +0600	[thread overview]
Message-ID: <87zgca42dn.fsf@disroot.org> (raw)
In-Reply-To: <jwv35a2hk37.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 28 Nov 2022 16:02:36 -0500")

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> 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?
>
> The problem goes much faster that the `nongnu.git` repository on
> `git.sv.gnu.org`, because that repository is tracked by several others.
> Can it be fixed?
> Yes, technically, but it's a pain in the rear to go and fix them all
> by hand.  It's only justified if there's a *real* problem (like the
> faulty commit contains something we *really* don't want to keep).
> Here, we're talking about including a commit with a suboptimal commit
> message.  Nobody will suffer from it,
>
>
>         Stefan
>

Thanks for the explanation, I'll merge from the diverged branch.

-- 
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 --]

      reply	other threads:[~2022-11-29  7:59 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
2022-11-28 21:02 ` Stefan Monnier
2022-11-29  7:59   ` Akib Azmain Turja [this message]

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=87zgca42dn.fsf@disroot.org \
    --to=akib@disroot.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).