From: Philip Kaludercic <philipk@posteo.net>
To: Stas Boukarev <notifications@github.com>
Cc: slime/slime <slime@noreply.github.com>,
slime/slime
<reply+ABQTI46LPH7JB5RM3A63UJ6DZ4YQFEVBNHHH4YOTTE@reply.github.com>,
Author <author@noreply.github.com>
Subject: Re: [slime/slime] Merge changes from ELPA (PR #809)
Date: Tue, 06 Feb 2024 10:12:50 +0000 [thread overview]
Message-ID: <87h6ilx5nh.fsf@posteo.net> (raw)
In-Reply-To: <slime/slime/pull/809/c1929127567@github.com> (Stas Boukarev's message of "Tue, 06 Feb 2024 01:40:18 -0800")
Stas Boukarev <notifications@github.com> writes:
> How does ELPA work that they a) can put random changes into their git
> b) can't remove them.
ELPA periodically mirrors upstream repositories, but the mirrors can
diverge. This is intentional, as sometimes we would like to make
changes to the upstream, when they are not responsive or the code has
been abandoned. In this case my understanding is that the commit on the
elpa/slime branch was pushed by accident.
I haven't tried it out, but I could imagine that force-pushing to the
branch could be possible, but that would require destructively modifying
the commit history of a public repository/branch, which one would like
to avoid -- hence the suggestion in the other pull request to reconcile
the conflict without making such drastic moves.
> Why should it be recommended to users if it's
> not reliable?
Do you mean ELPA by "it"? I would hesitate to say that this is an
indication of unreliability in general, it is just an issue that needs
resolving. Do you have any technical objections to the changes proposed
here that we could work out?
parent reply other threads:[~2024-02-06 10:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <slime/slime/pull/809/c1929127567@github.com>]
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=87h6ilx5nh.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=author@noreply.github.com \
--cc=notifications@github.com \
--cc=reply+ABQTI46LPH7JB5RM3A63UJ6DZ4YQFEVBNHHH4YOTTE@reply.github.com \
--cc=slime@noreply.github.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).