From: Pierre Tardy <tardyp@gmail.com>
To: Elijah Newren <newren@gmail.com>
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: Wed, 25 Sep 2019 15:36:39 +0200 [thread overview]
Message-ID: <CAJ+soVcmMwy7GgLcV-m1kNEsHYirHMQQeFuEYZanbCNUK4_zHg@mail.gmail.com> (raw)
In-Reply-To: <CABPp-BFXs4qes20S+9AZd++p3epW4eJ7Vu7zU_PdDysZ_D-yrg@mail.gmail.com>
> > As a community, our number one goal is for Git to continue to be the best
> > distributed version control system. At minimum, it should continue to be
> > the most widely-used DVCS.
>
> I'd rather we stated our goal in terms of what problems we are trying
> to address rather than accolades we want sent our way. E.g. "Our goal
> is to make developers more productive by providing them increasingly
> useful version control software".
>
Agreed.
And why restrict on DVCS?
Isn't it admitted that the distributed version control is nowadays
much better in term of software productivity?
Is there some use cases that "traditional" centralized VCS are better
on, and on which we gave up as a goal?
Regards,
Pierre
next prev parent reply other threads:[~2019-09-25 13:36 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 [this message]
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
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
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=CAJ+soVcmMwy7GgLcV-m1kNEsHYirHMQQeFuEYZanbCNUK4_zHg@mail.gmail.com \
--to=tardyp@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=newren@gmail.com \
--cc=peff@peff.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.
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).