From: wsnyder@wsnyder.org (Wilson Snyder)
To: Glenn Morris <rgm@gnu.org>
Cc: reto@gnu.org, emacs-devel@gnu.org
Subject: Re: Move verilog-mode and vhdl-mode to elpa.gnu.org
Date: Fri, 20 Feb 2015 23:25:00 -0500 [thread overview]
Message-ID: <7qr3tj51sz.fsf@emma.svaha.wsnyder.org> (raw)
Thanks for your suggestion to put verilog-mode into ELPA (I
can't speak for vhdl-mode).
I'll look into ELPA, it's certainly been many years since I
last considered it and it has improved massively.
BTW the only intentional difference between verilog-mode on
the veripool.org website and that in GNU Emacs is the
version number. Any other differences are squashed with
occasional merges; I merge Emacs trunk changes generally
within a few days, and for merges into trunk your work is
much appreciated.
However it's not clear to me how ELPA helps development this
as there would still two repos...
How does moving to ELPA simplify the process of merging the
package into Emacs trunk, is it scriped or something?
Likewise how do those edits made to the package in Emacs
trunk get back into the ELPA version? Feel free to just
point me to some FAQ about this if there is one.
Thanks
Glenn Morris <rgm@gnu.org> writes:
...
>I think a much better solution for everybody would be to move both these
>packages to elpa.gnu.org. If you are not familiar with this, it is a
>gnu.org package repository for Emacs lisp files. Other people on this
>list know much more about it than I do, and can hopefully ask any
>questions you might have.
...
next reply other threads:[~2015-02-21 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 4:25 Wilson Snyder [this message]
2015-02-21 20:24 ` Move verilog-mode and vhdl-mode to elpa.gnu.org Stefan Monnier
2015-02-24 6:37 ` Glenn Morris
-- strict thread matches above, loose matches on Subject: below --
2015-02-21 23:07 Wilson Snyder
2015-02-22 21:18 ` Stefan Monnier
2015-02-21 1:10 Glenn Morris
2015-02-21 1:12 ` Glenn Morris
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=7qr3tj51sz.fsf@emma.svaha.wsnyder.org \
--to=wsnyder@wsnyder.org \
--cc=emacs-devel@gnu.org \
--cc=reto@gnu.org \
--cc=rgm@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.