From: Francois Marier <francois@debian.org>
To: git@vger.kernel.org
Cc: sam.vilain@catalyst.net.nz
Subject: Suggestion: better error reporting when setting HEAD
Date: Thu, 18 Dec 2008 18:58:25 +1300 [thread overview]
Message-ID: <20081218055825.GQ6708@isafjordur.dyndns.org> (raw)
(Please CC me on your replies, thanks)
If you take any valid git repo and then do the following:
git symbolic-ref HEAD master
(instead of "git symbolic-ref HEAD refs/heads/master")
then other git commands (e.g. "git log") will return this error message:
fatal: Not a git repository
I'd like to suggest two "usability" improvements:
1- changing the error message to explain why the directory is no longer
considered a git repo. Maybe something along the lines of:
fatal: Invalid reference in .git/HEAD
2- To prevent this error from happening in the first place, git-symbolic-ref
could refuse to change HEAD to a non-existent ref.
Cheers,
Francois
next reply other threads:[~2008-12-18 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 5:58 Francois Marier [this message]
2008-12-18 8:25 ` Suggestion: better error reporting when setting HEAD 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081218055825.GQ6708@isafjordur.dyndns.org \
--to=francois@debian.org \
--cc=git@vger.kernel.org \
--cc=sam.vilain@catalyst.net.nz \
/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).