From: Adam <adamgsteel@gmail.com>
To: git@vger.kernel.org
Subject: Regular Rebase Failure
Date: Tue, 21 Apr 2015 11:16:16 -0600 [thread overview]
Message-ID: <553685E0.8010304@gmail.com> (raw)
About two weeks ago I started getting a regular rebase failure. I get this
error several times a day and at least once a day I lose work to it.
---
fatal: Unable to create '/Users/asteel/path/to/repo/.git/index.lock': File
exists.
If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.
Could not apply 71a...
---
The weird part is that the file does not exist
Any ideas? Thanks!
next reply other threads:[~2015-04-21 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 17:16 Adam [this message]
2015-04-21 17:51 ` Regular Rebase Failure Stefan Beller
[not found] ` <55369509.2080200@gmail.com>
2015-04-21 18:34 ` Stefan Beller
2015-04-21 21:15 ` Jeff King
[not found] ` <CAF72XQfVfjMLe2VqNWHkGXq75DLMPU6VVqLeGzgh9rZNC0qp3Q@mail.gmail.com>
2015-04-27 23:55 ` Stefan Beller
2015-04-29 15:14 ` Phil Hord
2015-04-29 15:22 ` Adam Steel
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=553685E0.8010304@gmail.com \
--to=adamgsteel@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 NNTP newsgroup(s).