git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Re* [PATCH] doc: glossary: add entry for revision range

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 18, 2021, 05:02 UTC
Message-ID
<60a34a7616cda_14d1bc20818@natae.notmuch>
In-Reply-To
<YKMhqZNhamnKqWfi@coredump.intra.peff.net>
Jeff King wrote:
Show 16 quoted lines
> 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
Previous: Felipe ContrerasNext: Jeff King
Message 15 of 19 in “doc: glossary: add entry for revision range”
  1. doc: glossary: add entry for revision rangeFelipe Contreras, May 16, 2021
  2. Re* [PATCH] doc: glossary: add entry for revision rangeJunio C Hamano, May 17, 2021
  3. Felipe ContrerasMay 17, 2021
  4. Jeff KingMay 17, 2021
  5. Felipe ContrerasMay 17, 2021
  6. Jeff KingMay 18, 2021
  7. Felipe ContrerasMay 18, 2021
  8. Junio C HamanoMay 17, 2021
  9. Felipe ContrerasMay 17, 2021
  10. Junio C HamanoMay 18, 2021
  11. Felipe ContrerasMay 18, 2021
  12. Jeff KingMay 18, 2021
  13. Junio C HamanoMay 18, 2021
  14. Felipe ContrerasMay 18, 2021
  15. Felipe ContrerasMay 18, 2021
  16. Jeff KingMay 18, 2021
  17. Felipe ContrerasMay 18, 2021
  18. Jeff KingMay 18, 2021
  19. Felipe ContrerasMay 18, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.