From: Junio C Hamano <gitster@pobox•com>
To: stephen_leake@stephe-leake•org
Cc: <git@vger•kernel.org>
Subject: Re: aborted 'git fetch' leaves workspace unusable
Date: Mon, 30 Dec 2013 11:37:25 -0800 [thread overview]
Message-ID: <xmqq8uv2ruyy.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <7adcf8024c435b9b7178b86f01e447bb@stephe-leake.org> (stephen leake's message of "Mon, 30 Dec 2013 10:07:55 -0700")
stephen_leake@stephe-leake•org writes:
> That left the workspace unusable:
>
> - .git/FETCH_HEAD is empty
>
> that causes 'git rev-parse FETCH_HEAD' to fail with a confusing
> error message.
This is not limited to your Cygwin environment. I can see that we
leave an empty file there after a failed fetch with
$ git fetch ssh://no.such.place/
But I would not call it leaving "the workspace unusable". If you
ask "git rev-parse" "What is in FETCH_HEAD?", you would get "that is
not even a revision", which is what you would get.
Similar operations that try to use FETCH_HEAD as if there is a valid
revision, e.g. "git merge FETCH_HEAD", would also not work, which is
very much expected. I wouldn't think that needs something drastic
as "this workspace is unusable, let's start from a new clone".
If it really bothers you, you can always safely do
$ rm -f .git/FETCH_HEAD
but of course, after that, nothing that tries to use FETCH_HEAD as
if there is a valid revision, e.g. "git show FETCH_HEAD", would not
work until you fetch from somewhere, so there isn't that much to be
gained by doing so.
> - 'git fetch' just hangs after outputting:
>
> remote: Counting objects: 15, done.
> remote: Compressing objects: 100% (8/8), done.
> remote: Total 9 (delta 5), reused 0 (delta 0)
This looks more serious, but I suspect it is totally unrelated to
your previous fetch failing and leaving FETCH_HEAD there. Is this
"'git fetch' hangs" reproduce in a clean clone _without_ first
encountering the failure (due to the forgotton "ssh-add")?
next prev parent reply other threads:[~2013-12-30 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 17:07 aborted 'git fetch' leaves workspace unusable stephen_leake
2013-12-30 19:37 ` Junio C Hamano [this message]
2013-12-30 19:54 ` Torsten Bögershausen
-- strict thread matches above, loose matches on Subject: below --
2013-12-31 8:19 stephen_leake
2014-01-02 18:09 ` Junio C Hamano
2014-01-03 3:28 ` Stephen Leake
2014-01-03 17:58 ` Junio C Hamano
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=xmqq8uv2ruyy.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=stephen_leake@stephe-leake$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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