From: "/#!/JoePea" <trusktr@gmail.com>
To: discuss@spectrum-os.org
Subject: Private GitLab for development?
Date: Thu, 9 Jan 2020 21:53:03 -0800 [thread overview]
Message-ID: <CAKU1PAXKJjmQ5=DWM8RWKKXbrg7Ez3oZO6TVO5_HnVoe65dCPg@mail.gmail.com> (raw)
This project is interesting!
Has a private instance of GitLab (or similar) been considered, to
promote contribution by online visibility and easier collaboration
(discussions in issues, pull requests, etc, similar GitHub).
I find email to be inefficient.
#!/JoePea
next reply other threads:[~2020-01-10 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 5:53 /#!/JoePea [this message]
2020-01-10 22:29 ` Alyssa Ross
[not found] ` <CAKU1PAWcDh-=DRWP7RR-oTD1QT1Siwq-iyEZx3RzoXjoVqMPbw@mail.gmail.com>
2020-01-12 20:28 ` Alyssa Ross
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='CAKU1PAXKJjmQ5=DWM8RWKKXbrg7Ez3oZO6TVO5_HnVoe65dCPg@mail.gmail.com' \
--to=trusktr@gmail.com \
--cc=discuss@spectrum-os.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 NNTP newsgroup(s).