From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: andre_pohlmann@posteo.de
Cc: git@vger.kernel.org
Subject: Re: bug or a general misunderstanding
Date: Wed, 10 Nov 2021 15:33:04 +0100 [thread overview]
Message-ID: <211110.868rxwhy9v.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <0bb0056a59cda294d416762d7f8a9c47@posteo.de>
On Wed, Nov 10 2021, andre_pohlmann@posteo.de wrote:
> 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
Hi there.
The mailing list you contacted is the Git development mailing list. I
think it's fair to assume that you haven't run into a bug in git, but
are in need of more basic resources on the topic of Git.
Git's pretty good at retaining your data, if you can't find it after
saving it in git the reason for why is likely to be explained by an
introductory tutorial.
A good resource to start with is: https://git-scm.com/community
next prev parent reply other threads:[~2021-11-10 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 12:00 bug or a general misunderstanding andre_pohlmann
2021-11-10 14:33 ` Ævar Arnfjörð Bjarmason [this message]
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=211110.868rxwhy9v.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=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).