From: Carlos <kaploceh@gmail.com>
To: git@vger.kernel.org
Subject: not robust inconsistent git 2.40.1 with HEAD -> master, origin/main, origin/HEAD, origin/master, main
Date: Tue, 30 May 2023 14:14:44 -0400 [thread overview]
Message-ID: <lxh4jpacuv5ivqp35w5vpbcjlw67r7ix3yog6cc3cu5ij7yqho@mrtr24xxdstx> (raw)
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
--
This login session: $13.99
next reply other threads:[~2023-05-30 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 18:14 Carlos [this message]
2023-05-31 10:08 ` not robust inconsistent git 2.40.1 with HEAD -> master, origin/main, origin/HEAD, origin/master, main Kristoffer Haugsbakk
2023-05-31 10:57 ` Philip Oakley
2023-05-31 13:22 ` Philip Oakley
2023-05-31 21:35 ` Carlos
2023-05-31 22:36 ` Carlos
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 17:58 Carlos
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=lxh4jpacuv5ivqp35w5vpbcjlw67r7ix3yog6cc3cu5ij7yqho@mrtr24xxdstx \
--to=kaploceh@gmail.com \
--cc=git@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).