From: Yoni Rabkin <yoni@rabkins.net>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: updating async on elpa
Date: Sat, 01 May 2021 09:05:25 -0400 [thread overview]
Message-ID: <87r1iqeh9m.fsf@rabkins.net> (raw)
In-Reply-To: <87lf8zrqym.fsf@posteo.net> (Thierry Volpiatto's message of "Sat, 01 May 2021 04:45:45 +0000")
Thierry Volpiatto <thievol@posteo.net> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> [[PGP Encrypted Part:OK]]
>>>>>> <user>@git.sv.gnu.org:/srv/git/emacs/elpa.git ?
>>>>> So no, it is not this,
>>>> Yes it it, but this only specifies the repository, not the branch.
>>> Hmm, I understand nothing how the elpa is structured, too complicated for me.
>>
>> When you push a branch you need to tell to which branch in the remote
>> repository you're pushing. The syntax is:
>>
>> git push <repository> <localbranch>:<remotebranch>
>>
>> so if you're pushing from your local `elpa` branch to elpa.git's
>> `externals/async` branch, then you need to do:
>>
>> git push elpa elpa:externals/async
>>
>> I suspect the problem is that you used a shorthand which works well when
>> the remote branch has the same name as a the local branch but can't be
>> used here.
>
> I will rename it to something else.
>
>> I'm not sure how much simpler we could make it. E.g. if we used
>> a separate repository per package, then presumably your `elpa` remote
>> would point to something like git.sv.gnu.org:emacs/elpa/async.git
>> and you'd need to push to the `main` branch in that repository, which
>> would still bring the same problem since the name `main` is still
>> different from the name `elpa` you used for your local branch.
>
> Yes, the name I use -elpa- is bad, but yes a repository per repo would be
> great, in github organizations allow having one repo per package like in
> helm organization.
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.
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. As
it stands, I'm always extremely wary that I would get the magical git
incantation wrong and mess up the the u.s. constitution and the magna
carta by mistake.
--
"Cut your own wood and it will warm you twice"
next prev parent reply other threads:[~2021-05-01 13:05 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 [this message]
2021-05-01 14:22 ` Stefan Monnier
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=87r1iqeh9m.fsf@rabkins.net \
--to=yoni@rabkins.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=thievol@posteo.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.