Stefan Monnier 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."