From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chitlesh GOORAH <chitlesh.goorah@gmail.com>
Cc: Reto Zimmermann <reto@gnu.org>, 5136@emacsbugs.donarmstrong.com
Subject: bug#5136: Request to update vhdl-mode and verilog-mode
Date: Sun, 6 Dec 2009 23:56:25 -0800 (PST) [thread overview]
Message-ID: <200912070756.nB77uOTF006336@godzilla.ics.uci.edu> (raw)
In-Reply-To: <50baabb30912061201l30cde8daua09bcefd7e5e3023@mail.gmail.com> (Chitlesh GOORAH's message of "Sun, 6 Dec 2009 21:01:24 +0100")
Chitlesh GOORAH <chitlesh.goorah@gmail.com> writes:
> Hello there,
>
> The following modes bundled in emacs-23.1-13.fc12.i686 are very old
> compared to the lastest upstream releases.
>
> vhdl-mode
> http://www.iis.ee.ethz.ch/~zimmi/emacs/vhdl-mode.html
Reto can you please send a patch + ChangeLog for the changes?
> verilog-mode
> http://www.verilog.com/verilog-mode.html
I've asked the authors for updates, they will be installed as soon as we
get them.
> I would like to request these to be updated within emacs sources so
> that linux distributions don't have to package them separately. This
> request is related to the work done behind Fedora Electronic Lab to
> give people a complete FOSS platform for micro-nanoelectronic design
> engineering, thus making emacs one of the core tools for mixed-signal
> hardware design, coupled with other emacs mode not included in the
> emacs sources.
Why isn't that mode included? What mode is it?
next prev parent reply other threads:[~2009-12-07 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 20:01 bug#5136: Request to update vhdl-mode and verilog-mode Chitlesh GOORAH
2009-12-07 7:56 ` Dan Nicolaescu [this message]
2009-12-07 8:50 ` Chitlesh GOORAH
2009-12-08 16:09 ` Dan Nicolaescu
2009-12-08 16:37 ` Reto Zimmermann
2009-12-08 17:51 ` Chitlesh GOORAH
2009-12-16 13:21 ` Reto Zimmermann
2009-12-16 13:39 ` Chitlesh GOORAH
2013-05-16 16:12 ` Glenn Morris
2009-12-08 16:30 ` Reto Zimmermann
2009-12-09 1:40 ` 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
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=200912070756.nB77uOTF006336@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=5136@emacsbugs.donarmstrong.com \
--cc=chitlesh.goorah@gmail.com \
--cc=reto@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 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).