From: Stephen Boyd <bebarino@gmail.com>
To: newren@gmail.com
Cc: git@vger.kernel.org, Johannes.Schindelin@gmx.de, kusambite@gmail.com
Subject: Re: [PATCH 2/7] Modify fast-export testcase to check that we correctly omit tags of trees
Date: Sat, 20 Jun 2009 22:53:27 -0700 [thread overview]
Message-ID: <4A3DCAD7.4030701@gmail.com> (raw)
In-Reply-To: <1245472623-28103-3-git-send-email-newren@gmail.com>
newren@gmail.com wrote:
> Should I have just squashed this with the previous patch? Or with the
> other testcase patch?
I think squashing it with the previous one is better as long as this is
directly related to patch 1.
>
> t/t9301-fast-export.sh | 8 +++++++-
> 1 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/t/t9301-fast-export.sh b/t/t9301-fast-export.sh
> index 8c8a9e6..d17f0e4 100755
> --- a/t/t9301-fast-export.sh
> +++ b/t/t9301-fast-export.sh
> @@ -272,7 +272,13 @@ test_expect_success 'set-up a few more tags for tag export tests' '
> '
>
> # NEEDSWORK: not just check return status, but validate the output
Is this comment still relevant?
> -test_expect_success 'tree_tag' 'git fast-export tree_tag'
> +test_expect_success 'tree_tag' '
> + mkdir result &&
> + cd result &&
> + git init &&
> + cd ..
> + git fast-export tree_tag | (cd result && git fast-import)
> +'
> test_expect_success 'tree_tag-obj' 'git fast-export tree_tag-obj'
> test_expect_success 'tag-obj_tag' 'git fast-export tag-obj_tag'
> test_expect_success 'tag-obj_tag-obj' 'git fast-export tag-obj_tag-obj'
I don't really know, but could test_create_repo() be useful here?
next prev parent reply other threads:[~2009-06-21 5:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 4:36 A few fast-export fixups newren
2009-06-20 4:36 ` [PATCH 1/7] fast-export: Omit tags that tag trees newren
2009-06-20 17:31 ` Jeff King
2009-06-20 18:01 ` Elijah Newren
2009-06-20 18:52 ` Jeff King
2009-06-20 4:36 ` [PATCH 2/7] Modify fast-export testcase to check that we correctly omit tags of trees newren
2009-06-21 5:53 ` Stephen Boyd [this message]
2009-06-21 6:17 ` Johannes Sixt
2009-06-22 13:12 ` Elijah Newren
2009-06-20 4:36 ` [PATCH 3/7] fast-export: Make sure we show actual ref names instead of "(null)" newren
2009-06-20 4:37 ` [PATCH 4/7] fast-export: Do parent rewriting to avoid dropping relevant commits newren
2009-06-20 4:37 ` [PATCH 5/7] fast-export: Add a --tag-of-filtered-object option for newly dangling tags newren
2009-06-20 4:37 ` [PATCH 6/7] Add new fast-export testcases newren
2009-06-20 4:37 ` [PATCH 7/7] fast-export: Document the fact that git-rev-list arguments are accepted newren
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=4A3DCAD7.4030701@gmail.com \
--to=bebarino@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kusambite@gmail.com \
--cc=newren@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.