From: "Jáchym Barvínek" <jachymb@gmail.com>
To: git@vger.kernel.org
Subject: Confusing git messages when disk is full.
Date: Sun, 12 Feb 2017 17:37:30 +0100 [thread overview]
Message-ID: <CABpqov=FE-h_2s=O9fkSjFjgFXSy6hDwc2fu5ijiVvkaLx9f_Q@mail.gmail.com> (raw)
Hello, I would like to report what I consider a bug in git, I hope I'm
doing it the right way.
I was trying to run `git pull` in my repository and got the following
error: "git pull
Your configuration specifies to merge with the ref 'refs/heads/master'
from the remote, but no such ref was fetched."
Which was very confusing to me, I found some answers to what might be the cause
but none was the right one. The actual cause was that the filesystem
had no more free space.
When I cleaned the space, `git pull` then gave the expected answer
("Already up-to-date.").
I think the message is confusing and git should be able to report to
the user that the cause
is full disk.
Regards, Jáchym Barvínek
next reply other threads:[~2017-02-12 16:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 16:37 Jáchym Barvínek [this message]
2017-02-15 21:32 ` Confusing git messages when disk is full Jeff King
2017-02-15 21:47 ` Junio C Hamano
2017-02-15 21:51 ` Jeff King
2017-02-15 22:28 ` Junio C Hamano
2017-02-15 22:32 ` Jeff King
2017-02-15 22:50 ` Junio C Hamano
2017-02-15 23:18 ` Jeff King
2017-02-16 10:10 ` Andreas Schwab
2017-02-16 16:44 ` Jeff King
2017-02-16 21:31 ` [PATCH] tempfile: avoid "ferror | fclose" trick Jeff King
2017-02-17 8:00 ` Michael Haggerty
2017-02-17 8:07 ` Jeff King
2017-02-17 10:42 ` Michael Haggerty
2017-02-17 20:54 ` Jeff King
2017-02-17 21:07 ` Jeff King
2017-02-17 21:17 ` Junio C Hamano
2017-02-17 21:21 ` Jeff King
2017-02-17 21:42 ` Junio C Hamano
2017-02-17 22:10 ` Jeff King
2017-02-17 22:40 ` Junio C Hamano
2017-02-17 23:39 ` Jeff King
2017-02-17 23:52 ` Junio C Hamano
2017-02-17 23:54 ` 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='CABpqov=FE-h_2s=O9fkSjFjgFXSy6hDwc2fu5ijiVvkaLx9f_Q@mail.gmail.com' \
--to=jachymb@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.
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).