All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Fonseca <fonseca@diku.dk>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org, torvalds@osdl.org
Subject: Re: New git commit tool
Date: Tue, 5 Sep 2006 18:46:52 +0200	[thread overview]
Message-ID: <20060905164652.GB5547@diku.dk> (raw)
In-Reply-To: <17660.40934.605502.248266@cargo.ozlabs.ibm.com>

Paul Mackerras <paulus@samba.org> wrote Tue, Sep 05, 2006:
> Jonas Fonseca writes:
> 
> >     I am a Cogito user, so I am no used to running git-update-index and
> >     this seems to be a problem in this case:
> > 
> > 	can't unset "indexpending(gitool)": no such element in array
> 
> Hmmm, I didn't think that could happen. :) It can only happen if some
> file gets listed twice in the output from "git-diff-index HEAD".
> Could you send me the output of "git-diff-index HEAD" and
> "git-diff-index --cached HEAD" in that repository?

~/gitool > git-diff-index HEAD
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
~/gitool > git-diff-index --cached HEAD
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
~/gitool > cat .git/HEAD
ref: refs/heads/master
~/gitool > ls .git/refs/heads/
~/gitool >

> And no, you don't need to run git-update-index, gitool does that for
> you.

Good to hear, but I swear the first time I ran gitool in a repo of mine
it popped up the error dialog with the details saying:

	fileX: needs update

Now, of course, I cannot reproduce it.

-- 
Jonas Fonseca

      reply	other threads:[~2006-09-05 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 11:52 New git commit tool Paul Mackerras
2006-09-04 12:26 ` Jakub Narebski
2006-09-04 17:10 ` Linus Torvalds
2006-09-04 21:20   ` Paul Mackerras
2006-09-04 21:40     ` Linus Torvalds
2006-09-05  8:45     ` Karl Hasselström
2006-09-04 19:57 ` Jonas Fonseca
2006-09-04 21:51   ` Paul Mackerras
2006-09-05 16:46     ` Jonas Fonseca [this message]

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=20060905164652.GB5547@diku.dk \
    --to=fonseca@diku.dk \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.