From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>, Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.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 00:02:46 -0500 [thread overview]
Message-ID: <60a34a7616cda_14d1bc20818@natae.notmuch> (raw)
In-Reply-To: <YKMhqZNhamnKqWfi@coredump.intra.peff.net>
Jeff King wrote:
> On Mon, May 17, 2021 at 04:05:41PM -0500, Felipe Contreras wrote:
>
> > > >> Nobody uses "origin" (what does that even mean?), [...]
> > > >
> > > > I guess I'm "nobody" then, because I use it all the time.
> > >
> > > Oh, I'm nobody, too, and so are many others ;-)
> >
> > That depends on the definition of "many". My guess is that it's less
> > than 1% of users (probably 0.01%), and for me that's not many.
> >
> > 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? The
> symlink is set up properly by git-clone, and has been for many years.
First instructions from GitHub:
echo "# test" >> README.md
git init
git add README.md
git commit -m "first commit"
git branch -M main
git remote add origin git@github.com:felipec/test.git
git push -u origin main
Second instructions from GitHub:
git remote add origin git@github.com:felipec/test.git
git branch -M main
git push -u origin main
None of these use `git clone`.
Of 31 repositories I work on and have quickly at hand only 8 have
origin/HEAD.
> 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).
On what do you base that guess?
The GitHub instructions don't use `git clone`. I can gather similar
instructions from other places if you are unconvinced.
I don't think most people set up their repositories as you think they
do.
And even *if* origin/HEAD did work on most repositories (hardly the
case), most people are not going to train their fingers to type `git cmd
$x` when the only $x where the command works is "origin"; they would
rather train their fingers to do $x/master which works on many more
repositories.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-18 5:03 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 [this message]
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
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=60a34a7616cda_14d1bc20818@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).