From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: mlang@delysid.org, emacs-devel@gnu.org
Subject: Re: [elpa] chess.el: Req. for comment/review: Info manual
Date: Thu, 19 Jun 2014 05:42:02 +0300 [thread overview]
Message-ID: <83a999tybp.fsf@gnu.org> (raw)
In-Reply-To: <jwv38f23qyb.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: mlang@delysid.org, emacs-devel@gnu.org
> Date: Wed, 18 Jun 2014 16:29:09 -0400
>
> Largish packages are better off in a separate "external" branch.
Why? The disadvantage is clear: it's more complicated to work with a
package that is on a branch. What are the advantages?
> > because it no longer fits the other packages in externals in
> > this respect.
>
> You mean like w3? rudel? dismal?
> auctex and ergoemacs-mode are the only two "external" packages which
> have some other upstream.
Then README needs some real rework.
next prev parent reply other threads:[~2014-06-19 2:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 19:23 [elpa] chess.el: Req. for comment/review: Info manual Mario Lang
2014-06-14 16:48 ` Eli Zaretskii
2014-06-14 18:48 ` Mario Lang
2014-06-14 19:08 ` Mario Lang
2014-06-14 19:24 ` Eli Zaretskii
2014-06-14 21:09 ` Stefan Monnier
2014-06-18 15:09 ` Eli Zaretskii
2014-06-18 18:09 ` Stefan Monnier
2014-06-18 18:34 ` Eli Zaretskii
2014-06-18 18:55 ` Stefan Monnier
2014-06-18 19:11 ` Eli Zaretskii
2014-06-18 20:29 ` Stefan Monnier
2014-06-19 2:42 ` Eli Zaretskii [this message]
2014-06-18 18:20 ` Mario Lang
2014-06-18 18:36 ` Eli Zaretskii
2014-06-18 18:58 ` Stefan Monnier
2014-06-18 19:13 ` Eli Zaretskii
2014-06-18 20:36 ` Stefan Monnier
2014-06-19 2:44 ` Eli Zaretskii
2014-06-19 15:18 ` Richard Stallman
2014-06-19 15:22 ` Eli Zaretskii
2014-06-18 19:20 ` Mario Lang
2014-06-18 20:36 ` Stefan Monnier
2014-06-19 3:37 ` Glenn Morris
2014-06-19 15:18 ` Eli Zaretskii
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=83a999tybp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mlang@delysid.org \
--cc=monnier@iro.umontreal.ca \
/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).