all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: Confusion about new format of ELPA repo
Date: Wed, 09 Dec 2020 21:39:45 +0100	[thread overview]
Message-ID: <87im9avhm6.fsf@gnus.org> (raw)
In-Reply-To: <87h7ouycyq.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 09 Dec 2020 11:51:57 -0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Maybe each package is now meant to be worked on in a separate branch?

Yes, every package in ELPA is now on its own branch, and only the files
from that package is present in that branch.  To take an example at
random:

larsi@xo:~/src/emacs/elpa$ git checkout externals/ack
Branch 'externals/ack' set up to track remote branch 'externals/ack' from 'origin'.
Switched to a new branch 'externals/ack'
larsi@xo:~/src/emacs/elpa$ ls
ack.el  csv-mode.elc  packages  pcmpl-ack.el  README.rst

If you have an ELPA checkout from before the structure was changed, it's
perhaps best to do a fresh checkout now to get rid of a bunch of
artefacts from the old layout.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2020-12-09 20:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 19:51 Confusion about new format of ELPA repo Eric Abrahamsen
2020-12-09 20:39 ` Lars Ingebrigtsen [this message]
2020-12-09 20:44   ` Lars Ingebrigtsen
2020-12-09 21:06     ` Eric Abrahamsen
2020-12-09 21:20       ` Stefan Monnier
2020-12-10  1:29         ` Eric Abrahamsen
2020-12-10 15:50           ` Stefan Monnier
2020-12-09 21:07   ` Stefan Monnier
2020-12-11 14:28     ` Lars Ingebrigtsen
2020-12-11 15:04       ` Stefan Monnier
2020-12-12  5:33       ` Richard Stallman
2020-12-12 13:40         ` Stefan Monnier
2020-12-13  5:00           ` Richard Stallman
2020-12-13  5:14             ` 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=87im9avhm6.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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.