From: Jonathan Nieder <jrnieder@gmail.com>
To: "\"Marcel 'childNo͡.de' Trautwein\"" <c0d3+gitscm@childno.de>
Cc: git@vger.kernel.org
Subject: Re: [BUG] [git 2.16.1] yeeek ... my files are gone .. by git pull <otherRepositoryUrl>
Date: Thu, 22 Feb 2018 15:20:31 -0800 [thread overview]
Message-ID: <20180222232031.GE256918@aiede.svl.corp.google.com> (raw)
In-Reply-To: <741A56BF-93C0-41EA-856F-C1170803F0A7@childno.de>
Hi Marcel,
Marcel 'childNo͡.de' Trautwein" wrote:
> I think we have a problem … or at least I had
> and I’m not quite sure if this is „working as designed“
> but I’m sure it „should not work as it did“.
[...]
> I wanted to clone another repository … but yeah … it’s late for me today and I put
> in s.th. `git pull git@private.gitlab.instance.example.com:aGroup/repository.git`
>
> next … all committed files are zapped and the repository given has
> been checked out in my home directory 🤯👻
>
> what? Shouldn’t this just fail? Why can I pass another remote to pull?
Sorry, this is not the most helpful reply but:
Can you describe a reproduction recipe so that I can experience the
same thing?
That is:
1. steps to reproduce
2. expected result
3. actual result
4. the difference and why it was unexpected
I suspect that this information is in your message, somewhere, but it
is (understandably) unfocussed and I am having trouble pulling it out.
[...]
> trying to fix this up by doing another pull failed:
> ```
> -bash:$ git remote -v
> origin git@bitbucket.org:childnode/marcel.git (fetch)
> origin git@bitbucket.org:childnode/marcel.git (push)
>
> -bash:$ git pull
> fatal: refusing to merge unrelated histories
Ok, this part is something I might be able to help shed some light on.
Searching for 'unrelated' in "git help pull" finds:
--allow-unrelated-histories
By default, git merge command refuses to merge histories that do not
share a common ancestor. This option can be used to override this
safety when merging histories of two projects that started their
lives independently. As that is a very rare occasion, no
configuration variable to enable this by default exists and will not
be added.
So that explains the "what" of that error message.
The "why" is a separate question. Could you share output from
git log --all --graph --decorate --oneline --simplify-by-decoration
and
git status
to help us understand your current state?
Also, suggestions for improvements to the 'refusing to merge' message
would be very welcome.
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2018-02-22 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 22:41 [BUG] [git 2.16.1] yeeek ... my files are gone .. by git pull <otherRepositoryUrl> "Marcel 'childNo͡.de' Trautwein"
2018-02-22 23:20 ` Jonathan Nieder [this message]
2018-02-23 5:29 ` "Marcel 'childNo͡.de' Trautwein"
2018-02-23 6:45 ` Jeff King
2018-02-26 23:33 ` Johannes Schindelin
2018-02-28 13:28 ` Jeff King
2018-03-05 14:49 ` Johannes Schindelin
2018-03-05 15:46 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180222232031.GE256918@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=c0d3+gitscm@childno.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).