All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Paul Tan <pyokagan@gmail.com>
Cc: git@vger.kernel.org,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Stefan Beller <sbeller@google.com>
Subject: Re: [PATCH v5 0/8] Improve git-pull test coverage
Date: Fri, 29 May 2015 11:08:10 -0700	[thread overview]
Message-ID: <xmqqk2vrcl4l.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1432899885-25143-1-git-send-email-pyokagan@gmail.com> (Paul Tan's message of "Fri, 29 May 2015 19:44:37 +0800")

Paul Tan <pyokagan@gmail.com> writes:

> This is a re-roll of [1].
>
> This patch series improves test coverage of git-pull.sh, and is part of my
> GSoC project to rewrite git-pull into a builtin. Improving test coverage
> helps to prevent regressions that could occur due to the rewrite.
>
> Thanks Junio, Johannes and Stefan for the reviews last round.
>
> [1] http://thread.gmane.org/gmane.comp.version-control.git/269236
>
> Paul Tan (8):
>   t5520: prevent field splitting in content comparisons
>   t5520: test no merge candidates cases
>   t5520: test for failure if index has unresolved entries
>   t5520: test work tree fast-forward when fetch updates head
>   t5520: test --rebase with multiple branches
>   t5520: test --rebase failure on unborn branch with index
>   t5521: test --dry-run does not make any changes
>   t5520: check reflog action in fast-forward merge
>
>  t/t5520-pull.sh         | 198 +++++++++++++++++++++++++++++++++++++++---------
>  t/t5521-pull-options.sh |  13 ++++
>  2 files changed, 175 insertions(+), 36 deletions(-)

I saw very little changes relative to the previous round, and all of
them looked sensible ones.

Thanks.

      parent reply	other threads:[~2015-05-29 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 11:44 [PATCH v5 0/8] Improve git-pull test coverage Paul Tan
2015-05-29 11:44 ` [PATCH v5 1/8] t5520: prevent field splitting in content comparisons Paul Tan
2015-05-29 11:44 ` [PATCH v5 2/8] t5520: test no merge candidates cases Paul Tan
2015-05-29 11:44 ` [PATCH v5 3/8] t5520: test for failure if index has unresolved entries Paul Tan
2015-05-29 11:44 ` [PATCH v5 4/8] t5520: test work tree fast-forward when fetch updates head Paul Tan
2015-05-29 11:44 ` [PATCH v5 5/8] t5520: test --rebase with multiple branches Paul Tan
2015-05-29 11:44 ` [PATCH v5 6/8] t5520: test --rebase failure on unborn branch with index Paul Tan
2015-05-29 11:44 ` [PATCH v5 7/8] t5521: test --dry-run does not make any changes Paul Tan
2015-05-29 11:44 ` [PATCH v5 8/8] t5520: check reflog action in fast-forward merge Paul Tan
2015-05-29 18:08 ` Junio C Hamano [this message]

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=xmqqk2vrcl4l.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=pyokagan@gmail.com \
    --cc=sbeller@google.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.