From: bill-auger <bill-auger@peers.community>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Issues on GitHub
Date: Wed, 27 Mar 2019 05:21:41 -0400 [thread overview]
Message-ID: <20190327052141.5da25cef@parabola> (raw)
In-Reply-To: <69a68e04-aeb2-793d-c3fa-737dc9510ffd@bluehome.net>
On Wed, 27 Mar 2019 01:05:58 -0500 Cal wrote:
> GitHub requires proprietary software (JavaScript).
most of the github website is functional with librejs, including
opening bug reports and commenting on existing ones
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2019-03-27 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 6:05 Issues on GitHub Cal
2019-03-27 9:21 ` bill-auger [this message]
2019-03-27 10:24 ` Issues on GitHub, " Dmitry Alexandrov
2019-03-27 13:51 ` Michael McMahon
2019-03-28 1:24 ` bill-auger
2019-03-27 14:45 ` Aaron Wolf
2019-03-28 1:51 ` Cal
2019-03-28 3:14 ` bill-auger
2019-03-28 4:06 ` Aaron Wolf
2019-03-28 12:52 ` Leah Rowe
2019-03-28 14:50 ` Matt Lee
2019-03-29 1:04 ` bill-auger
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://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190327052141.5da25cef@parabola \
--to=bill-auger@peers.community \
--cc=libreplanet-discuss@libreplanet.org \
/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 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).