From: Jonas Bernoulli <jonas@bernoul.li>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
"Eric Abrahamsen" <eric@ericabrahamsen.net>
Cc: Yuan Fu <casouri@gmail.com>,
Bozhidar Batsov <bozhidar@batsov.dev>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Don't add tags to ELPA packages -- documentation?
Date: Thu, 19 Aug 2021 22:54:08 +0200 [thread overview]
Message-ID: <87o89ti2a7.fsf@bernoul.li> (raw)
In-Reply-To: <871r6q1qu3.fsf@gmail.com>
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
Let's document that tags should not be pushed; both why and how,
as described elsewhere in this thread.
But I expect that tags will still occasionally be pushed anyway.
When that happens we should figure out what upstream repository
they came from, educate the respective maintainer about how to
avoid pushing them again, and then delete them.
But [because it is going to keep happening] this is more important:
> Mmm, IIUC any of "git clone", "git fetch" and "git pull" can fetch tags
> if not used with "--no-tags". A quick look at elpa-admin.el shows some
> occurrences of "pull" without "--no-tags", but I haven't looked hard
> enough at the GNU ELPA machinery to figure if those could have fetched
> the tags we observe.
Every occurrence of "git clone ..." and "git remote add ..." in the
documentation should be updated to mention that "--no-tags" has to be
used to prevent tags from being pulled. We should also document how to
recover if the tags have already been pulled. And finally we should add
an annotated tag named something like "use--no-tags" and use its
annotation to repeat the documentation about adding "--no-tags" and how
to clean up.
Jonas
next prev parent reply other threads:[~2021-08-19 20:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 21:10 Don't add tags to ELPA packages -- documentation? Eric Abrahamsen
2021-08-17 21:24 ` Stefan Monnier
2021-08-17 21:51 ` Eric Abrahamsen
2021-08-17 22:01 ` Adam Porter
2021-08-17 22:51 ` Eric Abrahamsen
2021-08-17 23:04 ` Stefan Monnier
2021-08-17 23:15 ` Phil Sainty
2021-08-17 23:28 ` Phil Sainty
2021-08-17 23:36 ` Eric Abrahamsen
2021-08-18 2:30 ` Phil Sainty
2021-08-18 6:41 ` Bozhidar Batsov
2021-08-18 7:03 ` Yuan Fu
2021-08-18 13:25 ` Stefan Monnier
2021-08-18 13:31 ` Stefan Monnier
2021-08-18 14:26 ` Kévin Le Gouguec
2021-08-18 14:33 ` Stefan Monnier
2021-08-18 15:52 ` Eric Abrahamsen
2021-08-18 16:56 ` Eric Abrahamsen
2021-08-18 19:43 ` Kévin Le Gouguec
2021-08-18 23:07 ` Stefan Monnier
2021-08-19 20:54 ` Jonas Bernoulli [this message]
2021-08-19 23:38 ` Eric Abrahamsen
2021-08-20 7:11 ` Andreas Schwab
2021-08-20 15:59 ` Eric Abrahamsen
2021-08-19 23:44 ` Eric Abrahamsen
2021-08-18 7:21 ` Phil Sainty
2021-08-18 8:15 ` Bozhidar Batsov
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=87o89ti2a7.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=bozhidar@batsov.dev \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=kevin.legouguec@gmail.com \
--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).