threads / discuss / 59808

not robust inconsistent git 2.40.1 with HEAD -> master, origin/main, origin/HEAD, origin/master, main

Subject: not robust inconsistent git 2.40.1 with HEAD -> master, origin/main, origin/HEAD, origin/master, main

## tl;dr

One message between May 30, 2023 and May 30, 2023.

replies: 0people: 1as markdown or json

Carlos· May 30, 2023, 17:58 UTC · lore
Running git 2.40.1 with HEAD -> master, origin/main, origin/HEAD, origin/master, main with initial commit on main does not show all the objects from master
! [main] Initial commit
 * [master] Initial commit
  ! [origin/master] Initial commit
---
+*+ [main] Initial commit

the chunk of objects are on master and not main, and yet it shows nothing once checking out to master.

the git-clone operation is not consistent either. It's a disaster.
One would think that by now with the more developed work put on to git, it'd
be safe to assume the more sense there's on newer versions. But no. This
 is the opposite actually. 
Now. If by any chance the git-branch operation were to return:
  main
* master
after git-clone, then objects are indeed in place. That is. On master
but not if git-branch returns 
  main
* master
  origin/master
-- 
Our documentation manager was showing her 2 year old son around the office.
He was introduced to me, at which time he pointed out that we were both
holding bags of popcorn.  We were both holding bottles of juice.  But only
*he* had a lollipop.
	He asked his mother, "Why doesn't HE have a lollipop?"
	Her reply: "He can have a lollipop any time he wants to.  That's
what it means to be a programmer."

← back to recent threads