git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Several fixes for the test suite related to spaces in filenames
Date: Wed, 3 Jan 2018 17:54:44 +0100 (STD)	[thread overview]
Message-ID: <cover.1514998470.git.johannes.schindelin@gmx.de> (raw)

The second issue was found long ago, and the patch carried in Git for
Windows, although nothing about it is specific to Windows.

The first patch was developed today, when I tried to verify that Git's
test suite passes if Git is cloned to a directory called `with spaces/`.


Johannes Schindelin (2):
  Allow the test suite to pass in a directory whose name contains spaces
  t0302 & t3900: add forgotten quotes

 t/t0302-credential-store.sh | 2 +-
 t/t3900-i18n-commit.sh      | 8 ++++----
 t/t7500-commit.sh           | 4 ++--
 t/t9020-remote-svn.sh       | 4 ++--
 t/t9107-git-svn-migrate.sh  | 2 +-
 5 files changed, 10 insertions(+), 10 deletions(-)


base-commit: 1eaabe34fc6f486367a176207420378f587d3b48
Published-As: https://github.com/dscho/git/releases/tag/with-spaces-v1
Fetch-It-Via: git fetch https://github.com/dscho/git with-spaces-v1
-- 
2.15.1.windows.2.391.g0b42e3c56de


             reply	other threads:[~2018-01-03 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 16:54 Johannes Schindelin [this message]
2018-01-03 16:54 ` [PATCH 1/2] Allow the test suite to pass in a directory whose name contains spaces Johannes Schindelin
2018-01-03 16:54 ` [PATCH 2/2] t0302 & t3900: add forgotten quotes Johannes Schindelin
2018-01-03 19:08 ` [PATCH 0/2] Several fixes for the test suite related to spaces in filenames Jeff King
2018-01-04  0:22   ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1514998470.git.johannes.schindelin@gmx.de \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).