unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thievol@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: updating async on elpa
Date: Fri, 30 Apr 2021 18:37:41 +0000	[thread overview]
Message-ID: <87o8dvty56.fsf@posteo.net> (raw)
In-Reply-To: <87y2czll5a.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]


Thierry Volpiatto <thievol@posteo.net> writes:

> [[PGP Signed Part:Good signature from 0EC56D141D16EF93 thievol@posteo.net (trust ultimate) created at 2021-04-30T19:47:29+0200 using RSA]]
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> [[PGP Encrypted Part:OK]]
>>>> so I think before pushing to `externals/async` someone will have to
>>>> merge the `elpa.git` changes into
>>>> https://github.com/jwiegley/emacs-async.
>>>
>>> I will try to do it, if I can get async from elpa.git, don't
>>> know how to get this for now.
>>
>> Assuming you're in a clone of `jwiegley/emacs-async`, you can do
>> something like:
>>
>>     git remote add -f -t externals/async elpa git://git.sv.gnu.org/emacs/elpa.git
>>     git merge elpa/externals/async
>
> Thanks, I could merge with many conflicts though, now I have to push,
> the address git://git.sv.gnu.org/emacs/elpa.git is the public address
> what is the equivalent with write access?
>
> <user>@git.sv.gnu.org:/srv/git/emacs/elpa.git ?

So no, it is not this, it seems it create again an elpa branch, please
remove it, sorry.
I give up to complicated.

-- 
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]

  parent reply	other threads:[~2021-04-30 18:37 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 [this message]
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
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

  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=87o8dvty56.fsf@posteo.net \
    --to=thievol@posteo.net \
    --cc=emacs-devel@gnu.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).