git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Paul Umbers <paul.umbers@gmail.com>, git@vger.kernel.org
Subject: Re: Git Cygwin - unable to create any repository - help!
Date: Wed, 16 Jan 2008 08:18:32 +0100	[thread overview]
Message-ID: <20080116071832.GA2896@steel.home> (raw)
In-Reply-To: <200801160002.51048.robin.rosenberg.lists@dewire.com>

Robin Rosenberg, Wed, Jan 16, 2008 00:02:49 +0100:
> tisdagen den 15 januari 2008 skrev Paul Umbers:
> > git ls (see below) returns nothing - it looks like the object doesn't
> > exist at all. I've attached a .zip of the entire test directory (one
> > text file plus .git). This is after "git init" followed by "git add ."
> > 
> > What do you think?
> 
> Git comes with test suite. Try it using make test or

He has just the precompiled packages from cygwin

> GIT_TEST_OPTS="--debug --verbose" make test
> 
> The extra options are there since we expect it to fail.
> 

But when compiled, it would be useflul indeed to see how the tests run

  reply	other threads:[~2008-01-16  7:19 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 [this message]
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=20080116071832.GA2896@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).