From: Pete Wyckoff <pw@padd.com>
To: Vitor Antunes <vitor.hda@gmail.com>
Cc: git@vger.kernel.org, Luke Diamand <luke@diamand.org>
Subject: Re: [PATCH 1/2] git-p4: Test changelists touching two branches
Date: Wed, 23 May 2012 21:08:05 -0400 [thread overview]
Message-ID: <20120524010805.GA26443@padd.com> (raw)
In-Reply-To: <1337729891-27648-2-git-send-email-vitor.hda@gmail.com>
vitor.hda@gmail.com wrote on Wed, 23 May 2012 00:38 +0100:
> It is possible to modify two different branches in P4 in a single
> changelist. git-p4 correctly detects this and commits the relevant
> changes to the different branches separately. This test proves that and
> avoid future regressions in this behavior.
>
> Signed-off-by: Vitor Antunes <vitor.hda@gmail.com>
> ---
> t/t9801-git-p4-branch.sh | 54 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 54 insertions(+), 0 deletions(-)
>
> diff --git a/t/t9801-git-p4-branch.sh b/t/t9801-git-p4-branch.sh
> index 2859256..89d8c59 100755
> --- a/t/t9801-git-p4-branch.sh
> +++ b/t/t9801-git-p4-branch.sh
> @@ -306,6 +306,60 @@ test_expect_success 'git p4 clone complex branches' '
> )
> '
>
> +# Move branch3/file3 to branch4/file3 in a single changelist
> +test_expect_success 'git p4 submit to two branches in a single changelist' '
> + test_when_finished cleanup_git &&
> + test_create_repo "$git" &&
You can skip the git bits here. This is just setup for the next
test.
Ack everything else. Nice to have the extra tests.
-- Pete
> + (
> + cd "$cli" &&
> + p4 integrate //depot/branch3/file3 //depot/branch4/file3 &&
> + p4 delete //depot/branch3/file3 &&
> + p4 submit -d "Move branch3/file3 to branch4/file3"
> + )
> +'
> +
> +# Confirm that changes to two branches done in a single changelist
> +# are correctly imported by git p4
> +test_expect_success 'git p4 sync changes to two branches in the same changelist' '
> + test_when_finished cleanup_git &&
> + test_create_repo "$git" &&
> + (
> + 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 &&
> + git p4 clone --dest=. --detect-branches //depot@all &&
> + git log --all --graph --decorate --stat &&
> + git reset --hard p4/depot/branch1 &&
> + test_path_is_file file1 &&
> + test_path_is_file file2 &&
> + test_path_is_file file3 &&
> + grep update file2 &&
> + git reset --hard p4/depot/branch2 &&
> + test_path_is_file file1 &&
> + test_path_is_file file2 &&
> + test_path_is_missing file3 &&
> + ! grep update file2 &&
> + git reset --hard p4/depot/branch3 &&
> + test_path_is_file file1 &&
> + test_path_is_file file2 &&
> + test_path_is_missing file3 &&
> + grep update file2 &&
> + git reset --hard p4/depot/branch4 &&
> + test_path_is_file file1 &&
> + test_path_is_file file2 &&
> + test_path_is_file file3 &&
> + ! grep update file2 &&
> + git reset --hard p4/depot/branch5 &&
> + test_path_is_file file1 &&
> + test_path_is_file file2 &&
> + test_path_is_file file3 &&
> + ! grep update file2 &&
> + test_path_is_missing .git/git-p4-tmp
> + )
> +'
> +
> test_expect_success 'kill p4d' '
> kill_p4d
> '
> --
> 1.7.7.rc2.14.g5e044.dirty
>
next prev parent reply other threads:[~2012-05-24 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 23:38 [PATCH 0/2] git-p4: New test cases for branch detection Vitor Antunes
2012-05-22 23:38 ` [PATCH 1/2] git-p4: Test changelists touching two branches Vitor Antunes
2012-05-24 1:08 ` Pete Wyckoff [this message]
2012-05-24 22:42 ` Vitor Antunes
2012-05-25 0:02 ` Junio C Hamano
2012-05-25 8:32 ` Vitor Antunes
2012-05-22 23:38 ` [PATCH 2/2] git-p4: Verify detection of "empty" branch creation Vitor Antunes
2012-05-24 1:13 ` Pete Wyckoff
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=20120524010805.GA26443@padd.com \
--to=pw@padd.com \
--cc=git@vger.kernel.org \
--cc=luke@diamand.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.