From: pedro rijo <pedrorijo91@gmail.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: James Ramsay <james@jramsay.com.au>, Git Users <git@vger.kernel.org>
Subject: Re: RFC - Git Developer Blog
Date: Tue, 17 Sep 2019 20:39:47 +0100 [thread overview]
Message-ID: <CAPMsMoDYHSD=+QiVU-+AfGnV+zJ309BRb7KRC4iDaOQ-9gMFEA@mail.gmail.com> (raw)
In-Reply-To: <20190917193233.GC17913@google.com>
Thanks for the explanation James :) Just wanted to understand if there
was any strong reason. As Emily said, we can easily move/mirror if we
find the need.
Thanks for starting up this project! If you need any help let me know
Emily Shaffer <emilyshaffer@google.com> escreveu no dia terça,
17/09/2019 à(s) 20:32:
>
> On Tue, Sep 17, 2019 at 03:22:38PM -0400, James Ramsay wrote:
> > 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.
>
> I really appreciate you setting it up, James - the starting inertia is
> one of the trickier bits of something like this :)
>
> If we decide later down the road that we really feel the need to have
> the site, book, translations, etc all in one place I think it'll be
> pretty trivial to mirror/move/whatever. I'm just happy to have somewhere
> to start!
>
> - Emily
--
Obrigado,
Pedro Rijo
next prev parent reply other threads:[~2019-09-17 19:40 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
2019-09-17 19:32 ` Emily Shaffer
2019-09-17 19:39 ` pedro rijo [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPMsMoDYHSD=+QiVU-+AfGnV+zJ309BRb7KRC4iDaOQ-9gMFEA@mail.gmail.com' \
--to=pedrorijo91@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=james@jramsay.com.au \
/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://80x24.org/mirrors/git.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).