From: "Bryan Donlan" <bdonlan@gmail.com>
To: "Adam Roben" <aroben@apple.com>
Cc: git@vger.kernel.org
Subject: Re: "make test" fails if /path/to/git.git contains spaces
Date: Mon, 31 Mar 2008 19:04:05 -0400 [thread overview]
Message-ID: <3e8340490803311604v52ab9e03nd101ccadd4973760@mail.gmail.com> (raw)
In-Reply-To: <47F15CDB.60109@apple.com>
On Mon, Mar 31, 2008 at 5:51 PM, Adam Roben <aroben@apple.com> wrote:
> I've noticed that "make test" fails if /path/to/git.git contains spaces,
> with the following error:
>
> > $ make test
> > make -C t/ all
> > make[1]: Entering directory `/home/Adam Roben/dev/git/t'
> > *** t0000-basic.sh ***
> > * error: cannot run git init -- have you built things yet?
> > make[1]: *** [t0000-basic.sh] Error 1
> > make[1]: Leaving directory `/home/Adam Roben/dev/git/t'
> > make: *** [test] Error 2
>
> This is a very common configuration on Cygwin, but clearly not a common
> configuration for git developers, or else this error would have been
> corrected already.
>
> Do we want to support having spaces in your path? It doesn't seem hard
> to fix, but it does seem like the kind of problem that will come up over
> and over again if only a very small set of people have this configuration.
Turns out that while trying to fix the tests, I've found that
git-rebase doesn't like a $VISUAL having spaces, so perhaps this
should be tested more often :) Or should we just require $VISUAL have
no spaces?
I'll send a patch once I've got everything passing.
Thanks,
Bryan
next prev parent reply other threads:[~2008-03-31 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 21:51 "make test" fails if /path/to/git.git contains spaces Adam Roben
2008-03-31 23:04 ` Bryan Donlan [this message]
2008-04-01 6:29 ` Johannes Sixt
2008-04-03 2:26 ` Bryan Donlan
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=3e8340490803311604v52ab9e03nd101ccadd4973760@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=aroben@apple.com \
--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 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).