all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Cc: reto@gnu.org, wsnyder@wsnyder.org
Subject: Move verilog-mode and vhdl-mode to elpa.gnu.org
Date: Fri, 20 Feb 2015 20:10:04 -0500	[thread overview]
Message-ID: <o7sie0gjdf.fsf@fencepost.gnu.org> (raw)


Hello verilog and vhdl mode maintainers,

Recently I've been trying to keep the version of these modes in Emacs
up-to-date with your versions. I'd prefer not to keep doing this (I don't
actually use either mode).

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.

One of the main advantages is that the files can be updated on your own
schedule, independent of the Emacs release cycle. This should make the
statement on http://www.veripool.org/projects/verilog-mode/wiki/Installing
about the Emacs version lagging the external version "by months to
years" a thing of the past! :)

Ideally, you would update the elpa.gnu.org versions yourselves.
It's essentially just a git repository. I believe there is some way to
add external branches; again, others can say more about this and the
best way to do it. I see verilog mode already use git. vhdl mode seems
to have no public VCS, which makes merging less than fun. Perhaps
elpa.gnu.org could be that VCS.

Anyway, regardless of the details, I think it's The Right Thing to Do.



             reply	other threads:[~2015-02-21  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21  1:10 Glenn Morris [this message]
2015-02-21  1:12 ` Move verilog-mode and vhdl-mode to elpa.gnu.org Glenn Morris
  -- strict thread matches above, loose matches on Subject: below --
2015-02-21  4:25 Wilson Snyder
2015-02-21 20:24 ` Stefan Monnier
2015-02-24  6:37 ` Glenn Morris
2015-02-21 23:07 Wilson Snyder
2015-02-22 21:18 ` Stefan Monnier

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=o7sie0gjdf.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=reto@gnu.org \
    --cc=wsnyder@wsnyder.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.