From: "Paul Umbers" <paul.umbers@gmail.com>
To: "Alex Riesen" <raa.lkml@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 14:44:10 -0700 [thread overview]
Message-ID: <a5eb9c330801161344i1da447c7sb447bf6274d408e8@mail.gmail.com> (raw)
In-Reply-To: <20080116191737.GD3181@steel.home>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Here's the log from the latest strace.
On Jan 16, 2008 12:17 PM, Alex Riesen <raa.lkml@gmail.com> wrote:
> 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
> >
>
> Could you please retry with "-m all"? "-m syscall" is not what one
> might expect, its some tracing of cygwin and not enough at that.
>
>
--
Computer Science is no more about computers than astronomy is about telescopes.
--- Edsger W. Dijkstra
Paul Umbers MSc MBCS MIAP
paul.umbers@gmail.com
[-- Attachment #2: log_2.tar.gz --]
[-- Type: application/x-gzip, Size: 35782 bytes --]
next prev parent reply other threads:[~2008-01-16 21:44 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
2008-01-16 19:17 ` Alex Riesen
2008-01-16 21:44 ` Paul Umbers [this message]
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=a5eb9c330801161344i1da447c7sb447bf6274d408e8@mail.gmail.com \
--to=paul.umbers@gmail.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@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).