git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-p4: warn if git authorship won't be retained

From
Junio C Hamano <gitster@pobox.com>
Date
May 10, 2011, 22:51 UTC
Message-ID
<7vhb92i2yu.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1305055653-5133-2-git-send-email-luke@diamand.org>
Luke Diamand <luke@diamand.org> writes:
Show 12 quoted lines
> diff --git a/t/t9800-git-p4.sh b/t/t9800-git-p4.sh
> index 4fb0e24..d6c7d13 100755
> --- a/t/t9800-git-p4.sh
> +++ b/t/t9800-git-p4.sh
> @@ -160,6 +160,15 @@ p4_check_commit_author() {
>      fi
>  }
>  
> +make_change_by_user() {
> +	file=$1
> +	name=$2
> +	email=$3
	file=$1 name=$2 email=$3 &&
Show 20 quoted lines
> +	echo "username: a change by $name" >> $file &&
> ...
> @@ -213,6 +222,43 @@ test_expect_success 'preserve user where author is unknown to p4' '
>  	rm -rf "$git" && mkdir "$git"
>  '
>  
> +# If we're *not* using --preserve-user, git-p4 should warn if we're submitting
> +# changes that are not all ours.
> +# Test: user in p4 and user unknown to p4.
> +# Test: warning disabled and user is the same.
> +test_expect_success 'not preserving user with mixed authorship' '
> +	"$GITP4" clone --dest="$git" //depot &&
> +	cd "$git" &&
> +	git config git-p4.skipSubmitEditCheck true
> +	p4_add_user derek Derek &&
> + ...
> +	p4_check_commit_author usernamefile3 alice &&
> +	cd "$TRASH_DIRECTORY" &&
> +	rm -rf "$git" && mkdir "$git"
> +'

When the commands in the && chain fails after 'cd "$git"' near the top but not before 'cd "$TRASH_DIRECTORY"' near the end, you would end up starting the next test from somewhere different from "$TRASH_DIRECTORY".

Do it like this instead:
	"$GITP4" clone --dest="$git" //depot &&
        (
        	cd "$git" &&
                ...
	) &&
        rm -fr "$git"
Previous: Luke DiamandNext: Luke Diamand
Message 4 of 6 in “git-p4: warn if git authorship won't be retained”
  1. git-p4: warn if git authorship won't be retainedLuke Diamand, May 10, 2011
  2. git-p4: warn if git authorship won't be retainedLuke Diamand, May 10, 2011
  3. Luke DiamandMay 10, 2011
  4. Junio C HamanoMay 10, 2011
  5. Luke DiamandMay 11, 2011
  6. Junio C HamanoMay 10, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.