From: andre_pohlmann@posteo.de
To: git@vger.kernel.org
Subject: bug or a general misunderstanding
Date: Wed, 10 Nov 2021 12:00:40 +0000 [thread overview]
Message-ID: <0bb0056a59cda294d416762d7f8a9c47@posteo.de> (raw)
Hello there
I'm not sure if I'm in the right place here.
Maybe it's a bug or a general misunderstanding of how GIT works.
The following situation: I wanted to create a branch from a commit. From
there on the work should be continued.
The possible bug:
The newly created branch is missing commits in the history. Not only are
they not displayed, the code changes are not present.
It doesn't matter if the branch is created by Visual Studio or GIT for
Windows.
Only in a branch created by GitHub Desktop the commits are present, as I
would expect.
Is this a bug or do I not understand how GIT works?
Best regards and thank you for the effort
André Pohlmann
next reply other threads:[~2021-11-10 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 12:00 andre_pohlmann [this message]
2021-11-10 14:33 ` bug or a general misunderstanding Ævar Arnfjörð Bjarmason
2021-11-10 14:46 ` Johannes Schindelin
2021-11-10 18:27 ` andre_pohlmann
[not found] ` <YY2MXSZXIRSDLQCu@camp.crustytoothpaste.net>
2021-11-15 10:56 ` andre_pohlmann
2021-11-15 21:08 ` Jeff King
2021-11-16 9:01 ` andre_pohlmann
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=0bb0056a59cda294d416762d7f8a9c47@posteo.de \
--to=andre_pohlmann@posteo.de \
--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 NNTP newsgroup(s).