From: Felipe Contreras <firstname.lastname@example.org>
To: Jeff King <email@example.com>, Felipe Contreras <firstname.lastname@example.org>
Cc: "Junio C Hamano" <email@example.com>,
firstname.lastname@example.org, "Nguyễn Thái Ngọc Duy" <email@example.com>,
"Richard Hansen" <firstname.lastname@example.org>
Subject: Re: Re* [PATCH] doc: glossary: add entry for revision range
Date: Tue, 18 May 2021 16:09:58 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
Jeff King wrote:
> On Tue, May 18, 2021 at 06:42:00AM -0500, Felipe Contreras wrote:
> > A random github.com link doesn't show anything. The instructions I'm
> > talking about are the **first** thing the site gives to users.
> I would think the first thing most users see is _somebody else's
> repository_, full of commits, that they then clone.
All the tutorials I've seen start with `git init`. If you want to learn
git starting from a monstrous repository such as Chrome OS is probably
not a good idea.
And yeah, if you assume most users are professional programmers, then
yeah, that's probably true. But that's an assumption.
Many users are students, others are amateur programmers, others might
be using git to track something other than code, like writing a book, or
Experts often forget what it is to be a beginner.
> > > People clone a lot more than they create new repositories.
> > Depends what you call "people". If you are talking about professional
> > software developers, then maybe.
> > But they are not the only users of git.
> > Do you have any stats?
> On one of GitHub's servers (selected randomly), there were ~300k clones
> in the past 24 hours. In the same time period on the same server, there
> were 1780 new repos. Even that's overstating it, since some portion of
> those are just forks of existing repos (so the user probably either
> cloned their fork immediately, or was already working on a clone of the
> upstream fork, rather than having run "git init" locally).
How do you distinguish a git clone from a git init + git remote add + git
> > > I don't think that proves anything except that your workflow is
> > > different than mine.
> > Exactly, and we cannot assume most people follow your workflow. In fact,
> > I'd say your workflow is probably one of the most atypical in the world.
> > You know tricks 99.99% of users don't know about, in fact that probably
> > 99% of git.git developers don't know.
> > It is sufficient to acknowledge that there are different workflows.
> I'm not making some bizarre claim about workflows. I'm saying that
> people commonly use "git clone" to get repositories. That really doesn't
> seem controversial.
It's not controversial, but it's also not necessarily true.
On what are you basing that claim?
> But you know what, I've wasted enough time on this thread. If you want
> to believe that people don't use "git clone", go for it.
I'll parse that as an answer to my quesion:
> > Is there anything that would falsify the premise?
"No, there's absolutely nothing that would falsify my premise".
If there's no way to falsify a claim, then there is no point in even
entertaining that claim.
prev parent reply other threads:[~2021-05-18 21:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 20:37 [PATCH] doc: glossary: add entry for revision range Felipe Contreras
2021-05-17 7:46 ` Re* " Junio C Hamano
2021-05-17 10:30 ` Felipe Contreras
2021-05-17 11:55 ` Jeff King
2021-05-17 17:22 ` Felipe Contreras
2021-05-18 6:59 ` Jeff King
2021-05-18 12:28 ` Felipe Contreras
2021-05-17 19:26 ` Junio C Hamano
2021-05-17 21:05 ` Felipe Contreras
2021-05-18 0:51 ` Junio C Hamano
2021-05-18 1:26 ` Felipe Contreras
2021-05-18 2:08 ` Jeff King
2021-05-18 2:57 ` Junio C Hamano
2021-05-18 5:20 ` Felipe Contreras
2021-05-18 5:02 ` Felipe Contreras
2021-05-18 6:55 ` Jeff King
2021-05-18 11:42 ` Felipe Contreras
2021-05-18 12:47 ` Jeff King
2021-05-18 21:09 ` Felipe Contreras [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.