From: Alex Riesen <raa.lkml@gmail.com>
To: Paul Umbers <paul.umbers@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Cygwin - unable to create any repository - help!
Date: Tue, 15 Jan 2008 23:55:36 +0100 [thread overview]
Message-ID: <20080115225536.GB32287@steel.home> (raw)
In-Reply-To: <a5eb9c330801151359q5a474a83le36ae9076ad4e5c1@mail.gmail.com>
Paul Umbers, Tue, Jan 15, 2008 22:59:52 +0100:
> Git version is 1.5.3.8.
That's ok too. The git-add is as verbose regarding errors as today.
Next would be to try to recompile git and instrument that file:
> On Jan 15, 2008 2:20 PM, Alex Riesen <raa.lkml@gmail.com> wrote:
> > Hmm... What "git version" returns for you? (the .git/config contains
> > filemode=true, which cygwin breaks every time).
> >
> > Of course, it would be interesting to know if the current git works
> > for you. Or the MinGW port:
> >
> > http://code.google.com/p/msysgit/downloads/list
> >
> > It used to conflict with cygwin, though.
Or try the MinGW port
> > If the current git fails, I'd suggest to instrument write_sha1_file in
> > sha1_file.c and see if it really manages to create temporary file and
> > rename it to sha1 file (that d9/b06fceac52f6c24357e6a7f85c601088381152).
> > I suspect either rename or link failing silently (IOW, it fails to
> > create the new name under objects/d9/ but returns 0(no error) anyway).
That sha1_file.c above
next prev parent reply other threads:[~2008-01-15 22:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 17:21 Git Cygwin - unable to create any repository - help! Paul Umbers
2008-01-14 20:29 ` Alex Riesen
2008-01-14 22:21 ` Paul Umbers
2008-01-15 5:48 ` Alex Riesen
2008-01-15 15:21 ` Paul Umbers
2008-01-15 20:04 ` Alex Riesen
2008-01-15 20:12 ` Paul Umbers
2008-01-15 21:20 ` Alex Riesen
2008-01-15 21:57 ` Paul Umbers
2008-01-15 22:51 ` Alex Riesen
2008-01-15 21:59 ` Paul Umbers
2008-01-15 22:55 ` Alex Riesen [this message]
2008-01-15 23:02 ` Robin Rosenberg
2008-01-16 7:18 ` Alex Riesen
2008-01-16 15:42 ` Paul Umbers
2008-01-16 17:55 ` Junio C Hamano
2008-01-16 18:10 ` Paul Umbers
2008-01-16 18:38 ` Alex Riesen
2008-01-16 18:57 ` Paul Umbers
2008-01-16 18:31 ` Alex Riesen
2008-01-16 18:48 ` Paul Umbers
2008-01-16 19:12 ` Alex Riesen
2008-01-16 19:17 ` Alex Riesen
2008-01-16 21:44 ` Paul Umbers
2008-01-16 23:45 ` Alex Riesen
2008-01-17 18:37 ` Paul Umbers
2008-01-17 18:51 ` Linus Torvalds
2008-01-17 19:17 ` Johannes Schindelin
2008-01-17 20:13 ` Paul Umbers
2008-01-17 20:24 ` Linus Torvalds
2008-01-17 20:38 ` Pascal Obry
2008-01-17 20:50 ` Johannes Schindelin
2008-01-17 20:53 ` Pascal Obry
2008-01-17 22:32 ` Paul Umbers
2008-01-17 20:18 ` Alex Riesen
2008-01-17 18:53 ` Nicholas Wourms
2008-01-17 20:30 ` Alex Riesen
2008-01-16 18:50 ` Paul Umbers
2008-01-15 17:08 ` Pascal Obry
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=20080115225536.GB32287@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=paul.umbers@gmail.com \
/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).