From: Eric Sunshine <sunshine@sunshineco.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3 1/6] t6300 (for-each-ref): clearly demarcate setup
Date: Sat, 16 Nov 2013 18:11:48 -0500 [thread overview]
Message-ID: <CAPig+cRz3_JSLJCu5AndSnreT91OqcQf_p+9-bUE5MUO_E066g@mail.gmail.com> (raw)
In-Reply-To: <1384513148-22633-2-git-send-email-artagnon@gmail.com>
On Fri, Nov 15, 2013 at 5:59 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Condense the two-step setup into one step, and give it an appropriate
> name.
>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
> t/t6300-for-each-ref.sh | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh
> index 752f5cb..72d282f 100755
> --- a/t/t6300-for-each-ref.sh
> +++ b/t/t6300-for-each-ref.sh
> @@ -18,16 +18,13 @@ setdate_and_increment () {
> export GIT_COMMITTER_DATE GIT_AUTHOR_DATE
> }
>
> -test_expect_success 'Create sample commit with known timestamp' '
> +test_expect_success setup '
> setdate_and_increment &&
> echo "Using $datestamp" > one &&
> git add one &&
> git commit -m "Initial" &&
> setdate_and_increment &&
> git tag -a -m "Tagging at $datestamp" testtag
Broken &&-chain here after these functions are combined.
> -'
> -
> -test_expect_success 'Create upstream config' '
> git update-ref refs/remotes/origin/master master &&
> git remote add origin nowhere &&
> git config branch.master.remote origin &&
> --
> 1.8.5.rc0.6.gfd75b41
next prev parent reply other threads:[~2013-11-16 23:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 10:59 [PATCH v3 0/6] Replacement for rr/for-each-ref-decoration Ramkumar Ramachandra
2013-11-15 10:59 ` [PATCH v3 1/6] t6300 (for-each-ref): clearly demarcate setup Ramkumar Ramachandra
2013-11-16 23:11 ` Eric Sunshine [this message]
2013-11-15 10:59 ` [PATCH v3 2/6] t6300 (for-each-ref): don't hardcode SHA-1 hexes Ramkumar Ramachandra
2013-11-15 10:59 ` [PATCH v3 3/6] for-each-ref: introduce %(HEAD) asterisk marker Ramkumar Ramachandra
2013-11-16 23:23 ` Eric Sunshine
2013-11-15 10:59 ` [PATCH v3 4/6] for-each-ref: introduce %(upstream:track[short]) Ramkumar Ramachandra
2013-11-16 23:53 ` Eric Sunshine
2013-11-17 5:58 ` Ramkumar Ramachandra
2013-11-15 10:59 ` [PATCH v3 5/6] for-each-ref: introduce %(color:...) for color Ramkumar Ramachandra
2013-11-17 0:04 ` Eric Sunshine
2013-11-15 10:59 ` [PATCH v3 6/6] for-each-ref: auto reset color after each atom Ramkumar Ramachandra
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=CAPig+cRz3_JSLJCu5AndSnreT91OqcQf_p+9-bUE5MUO_E066g@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).