From: Pete Wyckoff <pw@padd.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] git-p4: Add test case for complex branch import
Date: Mon, 16 Jan 2012 14:12:54 -0500 [thread overview]
Message-ID: <20120116191254.GB21996@padd.com> (raw)
In-Reply-To: <1326674360-2771-4-git-send-email-vitor.hda@gmail.com>
vitor.hda@gmail.com wrote on Mon, 16 Jan 2012 00:39 +0000:
> diff --git a/t/t9801-git-p4-branch.sh b/t/t9801-git-p4-branch.sh
> +test_expect_success 'git-p4 add complex branches' '
> + test_when_finished cleanup_git &&
> + test_create_repo "$git" &&
> + (
> + cd "$cli" &&
> + changelist=$(p4 changes -m1 //depot/... | cut -d" " -f2) &&
> + changelist=$((changelist - 5)) &&
> + p4 integrate //depot/branch1/...@$changelist //depot/branch4/... &&
> + p4 submit -d "branch4" &&
> + changelist=$((changelist + 2)) &&
> + p4 integrate //depot/branch1/...@$changelist //depot/branch5/... &&
> + p4 submit -d "branch5" &&
> + cd "$TRASH_DIRECTORY"
> + )
> +'
Sorry: I think I wanted the "$"s removed from inside $((..)).
Turns out that some shells don't grok that. The above should be:
changelist=$(($changelist - 5)) &&
You can drop the last cd to $TRASH_DIRECTORY since you're inside
a subshell. (Nice addition of the subshells.)
> +
> +# Configure branches through git-config and clone them. git-p4 will only be able
> +# to clone the original structure if it is able to detect the origin changelist
> +# of each branch.
> +test_expect_success 'git-p4 clone complex branches' '
> + test_when_finished cleanup_git &&
> + test_create_repo "$git" &&
> + (
> + test_when_finished cleanup_git &&
> + test_create_repo "$git" &&
These two lines can go; you already did it outside the subshell.
> + cd "$git" &&
> + git config git-p4.branchList branch1:branch2 &&
> + git config --add git-p4.branchList branch1:branch3 &&
> + git config --add git-p4.branchList branch1:branch4 &&
> + git config --add git-p4.branchList branch1:branch5 &&
> + "$GITP4" clone --dest=. --detect-branches //depot@all &&
> + git log --all --graph --decorate --stat &&
> + git reset --hard p4/depot/branch1 &&
> + test -f file1 &&
> + test -f file2 &&
> + test -f file3 &&
There are preferred functions for these tests, I learned recently:
test_path_is_file file1 &&
> + grep -q update file2 &&
> + git reset --hard p4/depot/branch2 &&
> + test -f file1 &&
> + test -f file2 &&
> + test ! -f file3 &&
Similarly
test_path_is_missing file3 &&
> + ! grep -q update file2 &&
> + git reset --hard p4/depot/branch3 &&
> + test -f file1 &&
> + test -f file2 &&
> + test -f file3 &&
> + grep -q update file2 &&
> + git reset --hard p4/depot/branch4 &&
> + test -f file1 &&
> + test -f file2 &&
> + test ! -f file3 &&
> + ! grep -q update file2 &&
> + git reset --hard p4/depot/branch5 &&
> + test -f file1 &&
> + test -f file2 &&
> + test -f file3 &&
> + ! grep -q update file2 &&
> + test ! -d .git/git-p4-tmp
> + )
> +'
prev parent reply other threads:[~2012-01-16 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 0:39 [PATCH 0/3] git-p4: Search for parent commit on branch creation Vitor Antunes
2012-01-16 0:39 ` [PATCH 1/3] git-p4: Add checkpoint() task Vitor Antunes
2012-01-16 0:39 ` [PATCH 2/3] git-p4: Search for parent commit on branch creation Vitor Antunes
2012-01-16 18:57 ` Pete Wyckoff
2012-01-16 23:41 ` Vitor Antunes
2012-01-17 0:10 ` Vitor Antunes
2012-01-17 22:18 ` Pete Wyckoff
2012-01-17 23:43 ` Vitor Antunes
2012-01-16 0:39 ` [PATCH 3/3] git-p4: Add test case for complex branch import Vitor Antunes
2012-01-16 19:12 ` Pete Wyckoff [this message]
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=20120116191254.GB21996@padd.com \
--to=pw@padd.com \
--cc=git@vger.kernel.org \
--cc=vitor.hda@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.