From: Michael Albinus <michael.albinus@gmx.de>
To: Robert Pluim <rpluim@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
Lars Ingebrigtsen <larsi@gnus.org>,
dick.r.chiang@gmail.com, emacs-devel@gnu.org
Subject: Re: bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread
Date: Wed, 20 Nov 2019 19:22:17 +0100 [thread overview]
Message-ID: <87sgmi5rxi.fsf@gmx.de> (raw)
In-Reply-To: <m2eey2v3ha.fsf@gmail.com> (Robert Pluim's message of "Wed, 20 Nov 2019 18:53:37 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> Iʼm going to have to go and read "How to commit to Elpa for dummies"
> now, aren't I? :-)
It's simple. The repository is at git.sv.gnu.org:/srv/git/emacs/elpa.git
After pulling, you call "make -k", because some of the packages don't
compile successfully.
If you want also to see the external packages, you need "make externals"
between "git pull" and "make -k". That's all.
> Robert
Best regards, Michael.
next prev parent reply other threads:[~2019-11-20 18:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87imnu1knq.fsf@dick>
[not found] ` <87r22h7mka.fsf@ericabrahamsen.net>
[not found] ` <87sgmrouxk.fsf@gnus.org>
[not found] ` <8736emaxw6.fsf@ericabrahamsen.net>
[not found] ` <87sgmlsgxx.fsf@gnus.org>
[not found] ` <87zhgsncno.fsf@ericabrahamsen.net>
[not found] ` <87lfscesen.fsf@dick>
[not found] ` <871ru4n58t.fsf@ericabrahamsen.net>
[not found] ` <m21ru4p3t8.fsf@gmail.com>
[not found] ` <87ftijdcay.fsf@ericabrahamsen.net>
[not found] ` <874kyykd8b.fsf@gnus.org>
[not found] ` <87sgmiyd6m.fsf@gmx.de>
[not found] ` <m2pnhmwwo7.fsf@gmail.com>
[not found] ` <87pnhmwvmz.fsf@gmx.de>
2019-11-20 13:31 ` bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread Robert Pluim
2019-11-20 13:43 ` Michael Albinus
2019-11-20 14:18 ` Robert Pluim
2019-11-20 14:30 ` Michael Albinus
2019-11-20 17:31 ` Robert Pluim
2019-11-20 17:45 ` Michael Albinus
2019-11-20 16:42 ` Eric Abrahamsen
2019-11-20 16:58 ` Robert Pluim
2019-11-20 17:01 ` Michael Albinus
2019-11-20 17:24 ` Robert Pluim
2019-11-20 17:34 ` Michael Albinus
2019-11-20 17:42 ` Robert Pluim
2019-11-20 17:51 ` Michael Albinus
2019-11-20 17:53 ` Robert Pluim
2019-11-20 18:22 ` Michael Albinus [this message]
2019-11-20 18:43 ` Eric Abrahamsen
2019-11-20 19:29 ` Robert Pluim
2019-11-20 16:59 ` Michael Albinus
2019-11-20 17:28 ` Robert Pluim
2019-11-20 17:43 ` Michael Albinus
2019-11-20 17:51 ` Robert Pluim
2019-11-20 17:59 ` Michael Albinus
2019-11-21 11:52 ` Lars Ingebrigtsen
2019-11-21 12:46 ` Michael Albinus
2019-11-21 13:03 ` Lars Ingebrigtsen
2019-11-21 14:54 ` Michael Albinus
2019-11-21 16:39 ` Robert Pluim
2019-11-22 8:30 ` Michael Albinus
2019-11-22 11:15 ` Robert Pluim
2019-11-22 11:41 ` Michael Albinus
2019-11-22 14:13 ` Robert Pluim
2019-11-22 16:33 ` Michael Albinus
2019-11-24 11:09 ` Michael Albinus
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=87sgmi5rxi.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=dick.r.chiang@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
/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).