From: Eric Wong <normalperson@yhbt.net>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git-svn: Fails to drop leading path from empty dir name
Date: Sun, 22 Nov 2009 15:25:04 -0800 [thread overview]
Message-ID: <20091122232504.GA28127@dcvr.yhbt.net> (raw)
In-Reply-To: <20091122134638.GA12233@atjola.homenet>
Björn Steinbrink <B.Steinbrink@gmx.de> wrote:
> Hi Eric,
>
> the stuff to create empty directories fails to strip leading path
> components, e.g. when using
> "git svn clone -s svn://whatever/project/trunk".
>
> Instead of creating the empty directory "foo" in the repo root, it
> creates "project/trunk/foo".
>
> Ad hoc patch for the test case below.
>
> Björn
>
> diff --git a/t/t9146-git-svn-empty-dirs.sh b/t/t9146-git-svn-empty-dirs.sh
> index 5948544..9e22089 100755
> --- a/t/t9146-git-svn-empty-dirs.sh
> +++ b/t/t9146-git-svn-empty-dirs.sh
> @@ -82,4 +82,27 @@ test_expect_success 'git svn mkdirs -r works' '
> )
> '
>
> +test_expect_success 'initialize trunk' '
> + for i in trunk trunk/a trunk/"weird file name"
> + do
> + svn_cmd mkdir -m "mkdir $i" "$svnrepo"/"$i"
> + done
> +'
> +
Hi Björn,
I'm having a bit of trouble figuring out exactly what you mean
here, can you double check your tests? Annotations below, thanks
> +test_expect_success 'clone trunk' 'git svn clone -s "$svnrepo" trunk'
^^ ^^^^^
Huh?
> +test_expect_success 'empty directories in trunk exist' '
> + (
> + cd cloned &&
^^^^^^ - ?
> + for i in trunk/a trunk/"weird file name"
> + do
> + if ! test -d "$i"
> + then
> + echo >&2 "$i does not exist"
> + exit 1
> + fi
> + done
--
Eric Wong
next prev parent reply other threads:[~2009-11-22 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 13:46 git-svn: Fails to drop leading path from empty dir name Björn Steinbrink
2009-11-22 23:25 ` Eric Wong [this message]
2009-11-22 23:52 ` Björn Steinbrink
2009-11-23 2:21 ` [PATCH] git svn: strip leading path when making empty dirs Eric Wong
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=20091122232504.GA28127@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=B.Steinbrink@gmx.de \
--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