From: Alex Riesen <raa.lkml@gmail.com>
To: Paul Umbers <paul.umbers@gmail.com>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>, git@vger.kernel.org
Subject: Re: Git Cygwin - unable to create any repository - help!
Date: Wed, 16 Jan 2008 20:12:50 +0100 [thread overview]
Message-ID: <20080116191250.GC3181@steel.home> (raw)
In-Reply-To: <a5eb9c330801161048x4b5a88dcsebd7cf9754f72ba6@mail.gmail.com>
Paul Umbers, Wed, Jan 16, 2008 19:48:28 +0100:
> Latest output, log file attached:
>
> paulumbers@Devteam29 ~/workspace/git/git-1.5.3
> $ uname -a > somefile
>
> paulumbers@Devteam29 ~/workspace/git/git-1.5.3
> $ git init
> Initialized empty Git repository in .git/
>
> paulumbers@Devteam29 ~/workspace/git/git-1.5.3
> $ strace -o log -f -m syscall ./git --exec-path=$(pwd) add somefile
>
> paulumbers@Devteam29 ~/workspace/git/git-1.5.3
> $ git ls-files -s somefile
> 100644 2ed63d326ffdb2fd4b703780f4d61f1893cac63b 0 somefile
>
> Checking .git/objects/2e ... there is no sha1 file
>
Hmm... Could you try to create a repo so that the whole path contains
no whitespace? Something like "c:/tmp/mydir". Just a suggestion, I am
still inspecting your log...
next prev parent reply other threads:[~2008-01-16 19:13 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
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 [this message]
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=20080116191250.GC3181@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=paul.umbers@gmail.com \
--cc=robin.rosenberg.lists@dewire.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).