From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Tassilo Horn <thorn@fastmail.fm>
Cc: "安宅 正之" <masayuki.ataka@gmail.com>,
"14596@debbugs.gnu.org" <14596@debbugs.gnu.org>,
"Masayuki Ataka" <masayuki.ataka+gnu@gmail.com>
Subject: bug#14596: 24.3.50; Error: Invalid read syntax: ". in wrong context" when compiling AUCTeX's tex-jp.el
Date: Fri, 14 Jun 2013 11:54:54 -0400 [thread overview]
Message-ID: <jwvppvo1yha.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y5acn6fu.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Fri, 14 Jun 2013 15:54:45 +0200")
> I still wouldn't object to migrating AUCTeX to the elpa repository, but
> I'd be equally happy if someone could provide something that lets me do
> AUCTeX ELPA releases easily. I'd prefer to release a new version every
> month rather than once every few years. Is it also possible to upload
> tarballs to ELPA, or is the packaging cron job handling the elpa branch
> the only way to get there?
Currently, the cron job is pretty limited, but we do need to add support
for separate repositories in any case.
This said, an important aspect of GNU ELPA is to make it so that it's
integrated in the Emacs development, so we will want to have a branch
hosted where Emacs maintainers have write access. This branch can be
made to auto-pull changes from upstream, but someone will have to
propagate the changes back from the elpa branch to upstream.
Stefan
next prev parent reply other threads:[~2013-06-14 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 6:59 bug#14596: 24.3.50; Error: Invalid read syntax: ". in wrong context" when compiling AUCTeX's tex-jp.el Tassilo Horn
2013-06-12 16:22 ` Glenn Morris
2013-06-12 17:40 ` Tassilo Horn
2013-06-12 21:13 ` 安宅 正之
2013-06-13 5:20 ` Glenn Morris
2013-06-13 21:30 ` 安宅 正之
2013-06-14 6:08 ` Tassilo Horn
2013-06-14 13:12 ` Stefan Monnier
2013-06-14 13:54 ` Tassilo Horn
2013-06-14 15:54 ` Stefan Monnier [this message]
2013-06-14 14:26 ` 安宅 正之
2013-06-12 21:10 ` 安宅 正之
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=jwvppvo1yha.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14596@debbugs.gnu.org \
--cc=masayuki.ataka+gnu@gmail.com \
--cc=masayuki.ataka@gmail.com \
--cc=thorn@fastmail.fm \
/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).