From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Yoni Rabkin <yoni@rabkins.net>
Cc: Thierry Volpiatto <thievol@posteo.net>, emacs-devel@gnu.org
Subject: Re: updating async on elpa
Date: Sat, 01 May 2021 10:22:30 -0400 [thread overview]
Message-ID: <jwvpmya4k4h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r1iqeh9m.fsf@rabkins.net> (Yoni Rabkin's message of "Sat, 01 May 2021 09:05:25 -0400")
> Having one repository per package is how it works everywhere else
> (Savannah, etc.), and is easier to understand because of that. This is
> from the point of view of a contributor of course; I cannot speak to how
> it looks from Stefan's side.
From my side it's plain and simply not an option at all because creating
a new repository on git.sv.gnu.org requires manual intervention from the
Savannah admins. Having had to design a solution that lives within this
constraint, I'm actually pretty happy about the current result, so if
the constraint were lifted, I'd probably want to try and preserve
the advantages.
In any case the `:auto-sync` feature should make it much less of an issue.
> I would be much happier if emms and rt-liberation had their own
> repositories since it would mean that I couldn't possibly break anything
> except emms or rt-liberation when I push to those projects in elpa.
The `elpa.git` is configured to reject non-fast-forward pushes, which
should catch most blunders. Plus it is cloned at various different
places which are not all constantly updated, plus (almost) all changes
to it are reflected in the elpa-diffs mailing-list. So even if you do
manage to make some really terrible mistake it should be quite easy to
recover from it.
You might want to activate the `:auto-sync` on your packages, tho to
save you from the worry.
Stefan
next prev parent reply other threads:[~2021-05-01 14:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 11:56 updating async on elpa Thierry Volpiatto
2021-04-30 14:17 ` Stefan Monnier
2021-04-30 15:20 ` Thierry Volpiatto
2021-04-30 16:21 ` Stefan Monnier
2021-04-30 17:42 ` Thierry Volpiatto
2021-04-30 18:36 ` Stefan Monnier
2021-04-30 18:42 ` Stefan Monnier
2021-04-30 18:37 ` Thierry Volpiatto
2021-04-30 18:48 ` Stefan Monnier
2021-04-30 19:31 ` Thierry Volpiatto
2021-04-30 20:21 ` Stefan Monnier
2021-05-01 4:45 ` Thierry Volpiatto
2021-05-01 13:05 ` Yoni Rabkin
2021-05-01 14:22 ` Stefan Monnier [this message]
2021-05-01 14:50 ` Thierry Volpiatto
2021-05-01 15:49 ` Stefan Monnier
2021-05-02 20:26 ` (was Re: updating async on elpa) auto-sync for emms Yoni Rabkin
2021-05-03 13:39 ` Stefan Monnier
2021-05-01 13:06 ` updating async on elpa Stefan Monnier
2021-05-01 14:38 ` Thierry Volpiatto
2021-05-01 15:37 ` Thierry Volpiatto
2021-05-01 17:11 ` Stefan Monnier
2021-05-01 18:01 ` Thierry Volpiatto
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=jwvpmya4k4h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=thievol@posteo.net \
--cc=yoni@rabkins.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.