From: Jakub Narebski <jnareb@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Derrick Stolee <stolee@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>,
"peff\@peff.net" <peff@peff.net>,
Emily Shaffer <emilyshaffer@google.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"gitster\@pobox.com" <gitster@pobox.com>,
garimasigit@gmail.com
Subject: Re: [DISCUSSION] Growing the Git community
Date: Fri, 04 Oct 2019 16:27:36 +0200 [thread overview]
Message-ID: <86muegoaav.fsf@gmail.com> (raw)
In-Reply-To: <20190920143614.GB20698@genre.crustytoothpaste.net> (brian m. carlson's message of "Fri, 20 Sep 2019 14:36:17 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I think GitGitGadget is a useful tool which I haven't really had the
> time to learn how to use. I appreciate that many people prefer a
> patch-based workflow, and that using a patch-based workflow and a
> mailing list provides the project independence and avoids favoring any
> hosting platform or tool, which I agree with.
>
> I think also that many folks find a pull request-based workflow to be
> easier and more familiar and supporting this a bit better may lower the
> barrier to entry, so I'm in favor of bridges that make contributing
> easier, even if one still needs to subscribe to the list to get
> feedback. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^
Actually you can get feedback without having to subscribe to git mailing
list; and I am not talking here about GitGitGadget gathering response
like GitHub Issues <-> mail bridge. You can get your feedback via
public-inbox.org, and respond to feedback via public-inboc.org mail to
[Usenet] news interface, reading and replying via NNTP (or replying via
email from thread read via NNTP):
nntp://news.public-inbox.org/inbox.comp.version-control.git
Unfortunately it looks like newsreaders are dying category of
applications. KDE's KNode got discontinued in 2015, XPN (X Python
Newsreader) last release had in 2009, MicroPlanet Gravity in 2010; there
is still Pan, Gnus for GNU Emacs; some e-mail clients also have support
for Usenet, like Mozilla Thunderbird (and SeaMonkey), Sylpheed and Claws
Mail.
This technique might not be described in our documentation...
Best,
--
Jakub Narębski
next prev parent reply other threads:[~2019-10-04 14:27 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 16:30 [DISCUSSION] Growing the Git community Derrick Stolee
2019-09-19 17:34 ` Denton Liu
2019-09-19 20:43 ` Emily Shaffer
2019-09-19 22:26 ` Jeff King
2019-09-20 17:48 ` Junio C Hamano
2019-09-20 15:22 ` Garima Singh
2019-09-20 17:51 ` Junio C Hamano
2019-09-19 18:44 ` Klaus Sembritzki
2019-09-19 19:12 ` Klaus Sembritzki
2019-09-19 20:20 ` Klaus Sembritzki
2019-09-20 5:04 ` Klaus Sembritzki
2019-09-20 5:41 ` Klaus Sembritzki
2019-09-20 6:54 ` Klaus Sembritzki
2019-09-20 7:43 ` Klaus Sembritzki
2019-09-20 10:25 ` Klaus Sembritzki
2019-09-19 21:40 ` Mike Hommey
2019-09-23 21:28 ` Johannes Schindelin
2019-10-01 15:03 ` Jakub Narebski
2019-09-19 22:16 ` Jeff King
2019-09-20 2:17 ` Derrick Stolee
2019-09-20 2:23 ` Jeff King
2019-09-19 22:21 ` Elijah Newren
2019-09-25 13:36 ` Pierre Tardy
2019-09-25 14:02 ` Derrick Stolee
2019-10-04 12:39 ` Jakub Narebski
2019-09-25 14:14 ` Philip Oakley
2019-10-04 10:48 ` Jakub Narebski
2019-11-12 18:45 ` Emily Shaffer
2019-11-12 20:01 ` Johannes Schindelin
2019-11-13 6:45 ` Christian Couder
2019-11-13 15:06 ` Thomas Gummerer
2019-11-14 2:31 ` Emily Shaffer
2019-11-14 6:06 ` Jeff King
2019-11-15 4:48 ` Junio C Hamano
2019-11-14 6:08 ` Pratyush Yadav
2019-11-14 10:01 ` Thomas Gummerer
2019-09-20 10:48 ` Philip Oakley
2019-09-20 14:36 ` brian m. carlson
2019-09-20 15:16 ` Randall S. Becker
2019-10-04 14:27 ` Jakub Narebski [this message]
2019-09-20 15:20 ` Garima Singh
2019-09-20 17:43 ` Junio C Hamano
2019-09-20 18:52 ` Junio C Hamano
2019-09-23 12:36 ` Derrick Stolee
2019-09-23 21:46 ` Johannes Schindelin
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=86muegoaav.fsf@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=garimasigit@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=stolee@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.
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.