From: "G. Sylvie Davies" <sylvie@bit-booster.com>
To: Git Users <git@vger.kernel.org>
Subject: not uptodate. Cannot merge
Date: Thu, 4 May 2017 14:40:12 -0700 [thread overview]
Message-ID: <CAAj3zPzHiwgS=2CSKP1y8zGUxHUWiq9TSeMhixeL+9ZfffY-pw@mail.gmail.com> (raw)
Hi,
My little bitbucket "cherry-pick" button is failing on Windows from a
"git reset --hard" blowing up.
My situation: Git-2.10.2.windows.1 / Bitbucket-4.14.3 / Windows
10-10.0-amd64. But I suspect even more recent Git will have the same
problem.
Now, I'm pretty far from Kansas here as you'll see from my "git clone"
invocation:
git.exe clone -c core.checkStat=minimal -c core.fileMode=false -c
core.ignoreStat=true -c core.trustctime=false -c
core.logAllRefUpdates=false --shared
C:\Users\gsylvie\dev\bb\target\bitbucket\home\shared\data\repositories\1
C:\Users\gsylvie\dev\bb\target\bitbucket\home\caches\bbClones\1
Right after cloning I create a ".git/info/attributes" file containing
just this one line:
* -text
After the clone, here's the sequence of commands leading up to the bad
"git reset --hard". These are all fine (well, the "--aborts" whine a
little, but that's expected):
git.exe branch --unset-upstream
git.exe update-index --refresh
git.exe rebase --abort
git.exe cherry-pick --abort
And here's the "git reset --hard" that fails:
git.exe reset --hard --quiet d6edcbf924697ab811a867421dab60d954ccad99 --
---
Exit=128
error: Entry 'basic_branching/file.txt' not uptodate. Cannot merge.
fatal: Could not reset index file to revision
'd6edcbf924697ab811a867421dab60d954ccad99'.
---
For now I've come up with an astonishing workaround: I just run "git
status" afterwards, and then everything is fine!
I'm going to limp along with this remedy, but I thought I'd share it
here in case anyone has any ideas, or in case it really is a bug.
- Sylvie
p.s. Thanks for mentioning "git-reverse.sh" in git rev news!
next reply other threads:[~2017-05-04 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 21:40 G. Sylvie Davies [this message]
2017-05-05 15:12 ` not uptodate. Cannot merge Johannes Schindelin
2017-05-05 15:25 ` Torsten Bögershausen
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='CAAj3zPzHiwgS=2CSKP1y8zGUxHUWiq9TSeMhixeL+9ZfffY-pw@mail.gmail.com' \
--to=sylvie@bit-booster.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.
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).