all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mario Lang <mlang@delysid.org>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] chess.el: Req. for comment/review: Info manual
Date: Wed, 18 Jun 2014 21:36:59 +0300	[thread overview]
Message-ID: <83ha3it67o.fsf@gnu.org> (raw)
In-Reply-To: <87r42m6pwh.fsf@fx.delysid.org>

> From: Mario Lang <mlang@delysid.org>
> Date: Wed, 18 Jun 2014 20:20:14 +0200
> 
> >   -   git clone --reference .. --single-branch --branch externals/PACKAGE git://git.sv.gnu.org/srv/git/emacs/elpa PACKAGE
> >   +   git clone --reference .. --single-branch --branch externals/PACKAGE $(git config remote.origin.url) PACKAGE
> >
> > is not necessarily for better: now this command and "make externals"
> > will do subtly different things, which not everyone will realize.  If
> > we want to be sure people with write access use the URL with write
> > access (and don't want to rely on them to know that and use the
> > correct URL), we should make changes to admin/archive-contents.el to
> > do that when all the externals are checked out.
> 
> Hmm, I changed just README since I tripped over this behaviour when
> using make externals.  I originally wanted to change the code run by
> make externals as well, but I was a bit too much chicken regarding me
> being new on ELPA :-).  Feel free to revert the one-liner in README if
> you think it is too confusing.  Or I will do that, if you feel strongly
> about it.

I'll let Stefan and Glenn do TRT, I no longer feel I understand what
is going on with elpa and the externals.  Why on earth did it have to
be so complicated?  Why did I need to read the Lisp source to figure
out how to checkout a single package from externals?



  reply	other threads:[~2014-06-18 18:36 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
2014-06-18 18:20   ` Mario Lang
2014-06-18 18:36     ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ha3it67o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mlang@delysid.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.