From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Don't add tags to ELPA packages -- documentation?
Date: Tue, 17 Aug 2021 14:10:22 -0700 [thread overview]
Message-ID: <87fsv7bww1.fsf@ericabrahamsen.net> (raw)
I just realized that you can't realistically add tags to your ELPA
packages, because tag names need to be unique across a repo, and your
"v0.6" is going to conflict with other packages' attempts to tag the
same. EBDB occupied some prime tag real estate with its earlier point
versions, but now I can't tag 0.7 because eglot already has that.
Can I patch the README to tell developers not to use tags at all? (You
can't even tag locally and not push them; git still complains.) Or is
there any other trick to solve the situation?
next reply other threads:[~2021-08-17 21:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 21:10 Eric Abrahamsen [this message]
2021-08-17 21:24 ` Don't add tags to ELPA packages -- documentation? 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsv7bww1.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
/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.