All of lore.kernel.org
 help / color / mirror / Atom feed
From: "srinivas naga vutukuri" <srinivas.vutukuri@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: problem using git on cygwin
Date: Wed, 2 May 2007 09:34:16 +0530	[thread overview]
Message-ID: <ace3f33d0705012104r3cf0b99ayb2ec2a69833e6ea1@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704301343020.29859@racer.site>

Hi,

On 4/30/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Mon, 30 Apr 2007, srinivas naga vutukuri wrote:
>
> > $ git add project/test.c
> > error: bad index file sha1 signature
> > fatal: index file corrupt
>
> I could imagine that you do not have "binary mode" default for opening
> files.
>

       i do't think it is in binary mode when opening the files. I am
used vim to create a new file and editing through that. And also am
used file format (set ff=unix).


> However, if you do, maybe your .git/index went corrupt?
>
> As a workaround, you could try "git read-tree HEAD" and then "git add"
> again, but make sure you have a backup of .git/index, since it could be a
> bug in Git(cygwin) and if so, I'd like to fix it.
>

     I have taken the initial index (once repository created, after
initial commit) to backup.
and followed the above steps.

1. cp index index.orig
2. git read-tree HEAD
3. git add test.c (my new file)

But end up with the same errors. Would you think there is a bug in the
git working on cygwin ?. I hope would the sequence help you in
catching the bug.



> Ciao,
> Dscho
>
>

best regards,
srinivas.

  reply	other threads:[~2007-05-02  4:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30  6:25 problem using git on cygwin srinivas naga vutukuri
2007-04-30 11:46 ` Johannes Schindelin
2007-05-02  4:04   ` srinivas naga vutukuri [this message]
2007-05-02 11:55     ` Jari Aalto
2007-05-02 12:37     ` Alex Riesen

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=ace3f33d0705012104r3cf0b99ayb2ec2a69833e6ea1@mail.gmail.com \
    --to=srinivas.vutukuri@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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 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.