From: Felipe Contreras <email@example.com>
To: Junio C Hamano <firstname.lastname@example.org>, Jeff King <email@example.com>
Cc: "Felipe Contreras" <firstname.lastname@example.org>,
email@example.com, "Nguyễn Thái Ngọc Duy" <firstname.lastname@example.org>,
"Richard Hansen" <email@example.com>
Subject: Re: Re* [PATCH] doc: glossary: add entry for revision range
Date: Tue, 18 May 2021 00:20:03 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Junio C Hamano wrote:
> Jeff King <email@example.com> writes:
> >> If you google for `git remote "set-head"` there's barely any
> >> information. It's basically all online man pages.
> > Why would people need to use "git remote set-head" most of the time?
> I somehow thought Felipe wanted to say that there is nothing but
> manual pages that mention the command and, "look how useful set-head
> subcommand is, here is how you use it" blog posts are not seen
> because nobody uses 'remote set-head'.
> I do not quesiotn the frequency count of set-head, but I do not
> think the lack of mention of set-head leads to the conclusion that
> nobody uses "git log origin.."; there is a leap in logic.
I did not say that is the only evidence to lead to that conclusion.
But it is evidence.
> As you said below, "origin" is there without need for set-head,
> so the lack of enthusiastic advocate for set-head does not mean
> anything wrt how people find "origin" useful.
Yes it does. Contrary to popular belief absence of evidence can be
evidence of absence. If I walk around Central Park for half an hour and
I don't see any elephants, that's evidence that there are no elephants
in Central Park at this very moment. It is not *conclusive* evidence,
but it is evidence.
Just because the evidence for $x is not sufficient to prove $x doesn't
mean there is no evidence for $x.
next prev parent reply other threads:[~2021-05-18 5:20 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 [this message]
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
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.