From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Felipe Contreras" <felipe.contreras@gmail.com>,
git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Richard Hansen" <rhansen@rhansen.org>
Subject: Re: Re* [PATCH] doc: glossary: add entry for revision range
Date: Tue, 18 May 2021 11:57:42 +0900 [thread overview]
Message-ID: <xmqq1ra44ul5.fsf@gitster.g> (raw)
In-Reply-To: YKMhqZNhamnKqWfi@coredump.intra.peff.net
Jeff King <peff@peff.net> 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. 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.
> The
> symlink is set up properly by git-clone, and has been for many years.
> For most people, using "origin" just works (the exception is people who
> "git init" and then "git remote add origin" themselves; since we're
> guessing at numbers, I would guess that _that_ population is less than
> 1% of users).
next prev parent reply other threads:[~2021-05-18 2:57 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 [this message]
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
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=xmqq1ra44ul5.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=rhansen@rhansen.org \
/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).