From: "James Ramsay" <james@jramsay.com.au>
To: "pedro rijo" <pedrorijo91@gmail.com>
Cc: "Git Users" <git@vger.kernel.org>
Subject: Re: RFC - Git Developer Blog
Date: Tue, 17 Sep 2019 15:22:38 -0400 [thread overview]
Message-ID: <45DA95BF-17D8-4238-9ECF-A4D1AC1A9634@jramsay.com.au> (raw)
In-Reply-To: <CAPMsMoAwfp+jv9h7xAD9PbqV+cU4njyf7Tex6HUCznqjb5hi_w@mail.gmail.com>
On 13 Sep 2019, at 10:05, pedro rijo wrote:
> Just a minor question: since we have git-scm, pro-git, and git
> translations in github, why not keep in the same place, under the same
> organization? I just find it easier to find than having repos
> scattered across different git hosting services
It wasn't a technical reason, but a matter of me (and my employer
GitLab) volunteering the time needed to get the blog project off the
ground. In the context of the Virtual Git Contributors' Summit, folks
seemed happy with using GitLab or any other service with a Git
interface.
next prev parent reply other threads:[~2019-09-17 19:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 1:49 RFC - Git Developer Blog Emily Shaffer
2019-08-06 3:33 ` Junio C Hamano
2019-08-06 4:59 ` Christian Couder
2019-08-06 13:27 ` Jeff King
2019-08-06 21:07 ` Emily Shaffer
2019-08-07 17:00 ` Taylor Blau
2019-08-06 4:52 ` Andrew Ardill
2019-08-06 12:19 ` Derrick Stolee
2019-08-06 21:00 ` Emily Shaffer
2019-08-07 17:12 ` Taylor Blau
2019-08-07 17:07 ` Taylor Blau
2019-08-07 17:15 ` Junio C Hamano
2019-08-07 17:44 ` Taylor Blau
2019-08-06 13:20 ` Jeff King
2019-08-06 20:49 ` Emily Shaffer
2019-09-13 13:29 ` James Ramsay
2019-09-13 14:05 ` pedro rijo
2019-09-17 19:22 ` James Ramsay [this message]
2019-09-17 19:32 ` Emily Shaffer
2019-09-17 19:39 ` pedro rijo
2019-10-23 22:36 ` James Ramsay
2019-10-23 23:48 ` Jeff King
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=45DA95BF-17D8-4238-9ECF-A4D1AC1A9634@jramsay.com.au \
--to=james@jramsay.com.au \
--cc=git@vger.kernel.org \
--cc=pedrorijo91@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 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).