git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rhodes, Kate" <masukomi@gmail.com>
To: git@vger.kernel.org
Subject: [Bug] git add -i fails in multiple ways prior to first commit.
Date: Mon, 11 Feb 2008 19:59:46 -0500	[thread overview]
Message-ID: <C50196C5-B0C5-4536-AD4A-0F9C553782EE@gmail.com> (raw)

$ git init
$ touch foo.txt
$ git add foo.txt
$ git add -i
fatal: bad revision 'HEAD'
            staged     unstaged path


*** Commands ***
   1: [s]tatus	  2: [u]pdate	  3: [r]evert	  4: [a]dd untracked
   5: [p]atch	  6: [d]iff	  7: [q]uit	  8: [h]elp
What now>


* status fails to report the current status
* update fails to work at all
* revert fails to work (not that there should be anything to revert  
but it shouldn't return a "fatal: bad revision 'HEAD'" message.
* add untracked works
* patch works
* diff fails
* help returns instructions that are incorrect owing to the fact that  
half of the things don't work in this state.
* quit, thankfully, works. :)


Why this is important:
git add's interactive mode is intended to make things easier, thus it  
stands to reason that people new to git are going to want to use it.  
Presenting them with so many broken commands so early on is,  
obviously, a really bad idea.

-masukomi

             reply	other threads:[~2008-02-12  1:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  0:59 Rhodes, Kate [this message]
2008-02-13 10:16 ` [Bug] git add -i fails in multiple ways prior to first commit Jeff King
2008-02-13 10:23   ` Jakub Narebski
2008-02-13 10:37     ` Jeff King
2008-02-13 10:50   ` [PATCH] add--interactive: handle initial commit better Jeff King
2008-02-13 11:25     ` Jeff King
2008-02-13 12:19       ` Johannes Schindelin
2008-02-13 13:11         ` Jakub Narebski
2008-02-13 13:15           ` Jeff King
2008-02-13 13:22           ` Johannes Schindelin
2008-02-13 13:45             ` Johannes Schindelin
2008-02-13 11:30   ` [Bug] git add -i fails in multiple ways prior to first commit Junio C Hamano
2008-02-13 11:34     ` 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=C50196C5-B0C5-4536-AD4A-0F9C553782EE@gmail.com \
    --to=masukomi@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).