git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "David A. Greene" <greened@obbligato.org>
Cc: git@vger.kernel.org, Techlive Zheng <techlivezheng@gmail.com>,
	James Nylen <jnylen@gmail.com>
Subject: Re: [PATCH 1/8] contrib/subtree: Use %B for split subject/body
Date: Mon, 18 Feb 2013 14:43:25 -0800	[thread overview]
Message-ID: <7va9r19raq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1361221013-12756-2-git-send-email-greened@obbligato.org> (David A. Greene's message of "Mon, 18 Feb 2013 14:56:46 -0600")

"David A. Greene" <greened@obbligato.org> writes:

> From: Techlive Zheng <techlivezheng@gmail.com>
>
> Use %B to format the commit message and body to avoid an extra newline
> if a commit only has a subject line.
>
> Signed-off-by: Techlive Zheng <techlivezheng@gmail.com>
> Signed-off-by: David A. Greene <greened@obbligato.org>
> ---
>  contrib/subtree/t/t7900-subtree.sh |   11 +++++++++++
>  1 file changed, 11 insertions(+)

Huh?

This seems to be a repeat of the test added in a5b8e28e4eb5
(contrib/subtree: use %B for split subject/body, 2013-02-04) and
nothing else, excluding the actual change to git-subtree itself.

Confused....

>
> diff --git a/contrib/subtree/t/t7900-subtree.sh b/contrib/subtree/t/t7900-subtree.sh
> index 80d3399..8dd6a82 100755
> --- a/contrib/subtree/t/t7900-subtree.sh
> +++ b/contrib/subtree/t/t7900-subtree.sh
> @@ -226,6 +226,17 @@ test_expect_success 'check hash of split' '
>  	check_equal ''"$new_hash"'' "$subdir_hash"
>  '
>  
> +test_expect_success 'check hash of split' '
> +        spl1=$(git subtree split --prefix subdir) &&
> +        undo &&
> +        git subtree split --prefix subdir --branch splitbr1test &&
> +        check_equal ''"$(git rev-parse splitbr1test)"'' "$spl1"
> +        git checkout splitbr1test &&
> +        new_hash=$(git rev-parse HEAD~2) &&
> +        git checkout mainline &&
> +        check_equal ''"$new_hash"'' "$subdir_hash"
> +'
> +
>  test_expect_success 'check split with --branch for an existing branch' '
>          spl1=''"$(git subtree split --annotate='"'*'"' --prefix subdir --onto FETCH_HEAD --message "Split & rejoin" --rejoin)"'' &&
>          undo &&

  reply	other threads:[~2013-02-18 22:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 20:56 Subtree Fixes Updates David A. Greene
2013-02-18 20:56 ` [PATCH 1/8] contrib/subtree: Use %B for split subject/body David A. Greene
2013-02-18 22:43   ` Junio C Hamano [this message]
2013-02-18 20:56 ` [PATCH 2/8] contrib/subtree: Fix whitespaces David A. Greene
2013-02-18 20:56 ` [PATCH 3/8] contrib/subtree: Ignore testing directory David A. Greene
2013-02-18 22:51   ` Junio C Hamano
2013-02-18 20:56 ` [PATCH 4/8] contrib/subtree: Code cleaning and refactoring David A. Greene
2013-02-18 22:55   ` Junio C Hamano
2013-02-18 20:56 ` [PATCH 5/8] contrib/subtree: Make each test self-contained David A. Greene
2013-02-18 20:56 ` [PATCH 6/8] contrib/subtree: Handle '--prefix' argument with a slash appended David A. Greene
2013-02-18 20:56 ` [PATCH 7/8] contrib/subtree: Remove --annotate David A. Greene
2013-02-18 20:56 ` [PATCH 8/8] Remove test artifaces from clean rule David A. Greene

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=7va9r19raq.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=greened@obbligato.org \
    --cc=jnylen@gmail.com \
    --cc=techlivezheng@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 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).