From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Ergus <spacibba@aol.com>, emacs-devel@gnu.org
Subject: Re: [RFC] Urgrep: New ELPA submission (eventually)
Date: Sat, 04 Feb 2023 17:22:09 -0500 [thread overview]
Message-ID: <jwv1qn59ip3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <d6613829-042d-b934-8ee2-516f8cfff8cf@gmail.com> (Jim Porter's message of "Sat, 4 Feb 2023 11:44:12 -0800")
> First, assigning copyright of Urgrep to the FSF (so that it can go in GNU
> ELPA) is just a matter of updating the copyright field in the code, right?
> Do I need to fill out any paperwork or anything too?
You basically need to "state" that you consider that code to be covered
by your existing Emacs assignment. We usually consider that changing
the copyright line in the files is a valid way to make this statement.
> Second, my usual process for versioning is that I'll release a version like
> "1.0" by updating the "Version:" field and tagging it. Then, in the next
> commit, I update the "Version:" field to something like "2.0-snapshot". So
> in this case, I'd expect GNU ELPA to give users version 1.0, and GNU
> ELPA-devel to give users the latest 2.0-snapshot version. Does ELPA
> understand that?
Yes.
Stefan
next prev parent reply other threads:[~2023-02-04 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 4:18 [RFC] Urgrep: New ELPA submission (eventually) Jim Porter
2022-09-12 12:58 ` Stefan Monnier
2022-09-14 4:52 ` Jim Porter
2023-02-04 17:12 ` Ergus
2023-02-04 19:44 ` Jim Porter
2023-02-04 21:37 ` Ergus
2023-02-04 22:22 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 4:56 Jim Porter
2022-09-12 9:19 ` Stefan Kangas
2022-09-12 17:05 ` Jim Porter
2022-09-12 11:11 ` Eli Zaretskii
2022-09-12 18:00 ` Jim Porter
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=jwv1qn59ip3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=spacibba@aol.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 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.