From: dick.r.chiang@gmail.com
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 38136@debbugs.gnu.org
Subject: bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread
Date: Sat, 14 Dec 2019 11:22:01 -0500 [thread overview]
Message-ID: <877e2yj2s6.fsf@dick> (raw)
In-Reply-To: <871ru4n58t.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 18 Nov 2019 15:18:10 -0800")
EA> If you have access to the Emacs repos and are collaborating with others
EA> who do, too, then it can make sense to push a "feature/foo" branch to the
EA> repos, and share it.
Someone was somehow able to upload a gnus feature branch in the
official repo and get core devs to test it.
It's described here
https://lists.gnu.org/archive/html/emacs-devel/2019-10/msg00689.html.
Is this what you're referring to when you say "push a feature/foo"
branch? Currently when I "git clone http://git.sv.gnu.org/git/emacs.git", git just
hangs.
next prev parent reply other threads:[~2019-12-14 16:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 14:56 bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread dick.r.chiang
2019-11-09 3:31 ` Eric Abrahamsen
2019-11-14 6:04 ` Lars Ingebrigtsen
2019-11-17 23:25 ` Eric Abrahamsen
2019-11-18 8:54 ` Lars Ingebrigtsen
2019-11-18 20:38 ` Eric Abrahamsen
2019-11-18 22:22 ` dick.r.chiang
2019-11-18 23:18 ` Eric Abrahamsen
2019-11-19 10:18 ` Robert Pluim
2019-11-19 17:08 ` Eric Abrahamsen
2019-11-20 11:18 ` Lars Ingebrigtsen
2019-11-20 11:55 ` Michael Albinus
2019-11-20 12:37 ` Robert Pluim
2019-11-20 13:00 ` Michael Albinus
2019-12-14 16:22 ` dick.r.chiang [this message]
2019-12-14 19:38 ` Eric Abrahamsen
2021-05-12 15:52 ` Lars Ingebrigtsen
2021-05-12 16:30 ` dick.r.chiang
2019-11-12 10:01 ` bug#38136: [PATCH] Make gnus-group-get-new-news a non blocking thread, " Robert Pluim
2019-11-25 17:50 ` bug#38136: https://github.com/dickmao/gnus dick.r.chiang
2019-11-25 19:02 ` Eric Abrahamsen
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=877e2yj2s6.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=38136@debbugs.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 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).