git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-am: teach git-am to apply a patch to an unborn branch
Date: Thu, 19 Mar 2009 15:21:17 -0700	[thread overview]
Message-ID: <7viqm56tnm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090320071231.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Fri, 20 Mar 2009 07:12:31 +0900")

Nanako Shiraishi <nanako3@lavabit.com> writes:

> Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com>
> ---
>  git-am.sh     |   33 ++++++++++++++++++++++++++++-----
>  t/t4150-am.sh |   15 +++++++++++++++
>  2 files changed, 43 insertions(+), 5 deletions(-)
>
> diff --git a/git-am.sh b/git-am.sh
> index d339075..c21642b 100755
> --- a/git-am.sh
> +++ b/git-am.sh
> @@ -36,6 +36,13 @@ cd_to_toplevel
>  git var GIT_COMMITTER_IDENT >/dev/null ||
>  	die "You need to set your committer info first"
>  
> +if git rev-parse --verify -q HEAD >/dev/null
> +then
> +	HAS_HEAD=yes
> +else
> +	HAS_HEAD=
> +fi
> +

Probably nicer this way than Peff's as I suspect we would need to special
case the unborn-branch case a lot more.  Have you tried --skip and --abort
codepaths with your patch?

>  sq () {
>  	for sqarg
>  	do
> @@ -290,16 +297,26 @@ else
>  		: >"$dotest/rebasing"
>  	else
>  		: >"$dotest/applying"
> -		git update-ref ORIG_HEAD HEAD
> +		if test -n "$HAS_HEAD"
> +		then
> +			git update-ref ORIG_HEAD HEAD
> +		else
> +			git update-ref -d ORIG_HEAD >/dev/null 2>&1
> +		fi

So is this part.

>  	fi
>  fi
>  
>  case "$resolved" in
>  '')
> -	files=$(git diff-index --cached --name-only HEAD --) || exit
> +	if test -n "$HAS_HEAD"
> +	then
> +		files=$(git diff-index --cached --name-only HEAD --)
> +	else
> +		files=$(git ls-files)
> +	fi || exit
>  	if test "$files"
>  	then
> -		: >"$dotest/dirtyindex"
> +		test -n "$HAS_HEAD" && : >"$dotest/dirtyindex"
>  		die "Dirty index: cannot apply patches (dirty: $files)"
>  	fi
>  esac

And here...

> @@ -541,7 +558,13 @@ do
>  	fi
>  
>  	tree=$(git write-tree) &&
> -	parent=$(git rev-parse --verify HEAD) &&
> +	if parent=$(git rev-parse --verify -q HEAD)
> +	then
> +		pparent="-p $parent"
> +	else
> +		echo >&2 "applying to an empty history"
> +		parent= pparent=
> +	fi &&
>  	commit=$(
>  		if test -n "$ignore_date"
>  		then
> @@ -552,7 +575,7 @@ do
>  			GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"
>  			export GIT_COMMITTER_DATE
>  		fi &&
> -		git commit-tree $tree -p $parent <"$dotest/final-commit"
> +		git commit-tree $tree $pparent <"$dotest/final-commit"

Peff's ${a+something $a} trick looks more "expert" here ;-).

> diff --git a/t/t4150-am.sh b/t/t4150-am.sh
> index 5e65afa..b97d102 100755
> --- a/t/t4150-am.sh
> +++ b/t/t4150-am.sh
> @@ -290,4 +290,19 @@ test_expect_success 'am --ignore-date' '
>  	echo "$at" | grep "+0000"
>  '
>  
> +test_expect_success 'am in an unborn branch' '
> +	rm -fr subdir &&
> +	mkdir -p subdir &&
> +	git format-patch --numbered-files -o subdir -1 first &&
> +	(
> +		cd subdir &&
> +		git init &&
> +		git am 1
> +	) &&
> +	result=$(
> +		cd subdir && git rev-parse HEAD^{tree}
> +	) &&
> +	test "z$result" = "z$(git rev-parse first^{tree})"
> +'
> +

Looks good.

  reply	other threads:[~2009-03-19 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 22:12 [PATCH] git-am: teach git-am to apply a patch to an unborn branch Nanako Shiraishi
2009-03-19 22:21 ` Junio C Hamano [this message]
2009-03-20  4:37 ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2009-04-10  0:34 Nanako Shiraishi
2009-04-13  3:46 ` 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

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

  git send-email \
    --in-reply-to=7viqm56tnm.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nanako3@lavabit.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 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 NNTP newsgroup(s).