git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] CI: Enable t1509 on GitHub Actions and Travis
Date: Wed, 13 May 2020 09:41:49 -0700	[thread overview]
Message-ID: <xmqqh7wjvlbm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <cover.1589375923.git.congdanhqx@gmail.com> ("Đoàn Trần Công Danh"'s message of "Wed, 13 May 2020 20:23:05 +0700")

Đoàn Trần Công Danh  <congdanhqx@gmail.com> writes:

> It's our long desire to enable t1509 in CI system [1]
>
> This is here to enable it.

Yuck.

It's not like having a single repository at /.git that govern
everything on the machine is a usecase we care about, but if it is
easily ported with just two patches, and the task has already been
done, then why not?  ;-)




>
> [1]: https://lore.kernel.org/git/1FEDCA48-FE77-44C3-8C4A-65B4C435E6B3@gmail.com/
>
> Đoàn Trần Công Danh (2):
>   t1509: correct i18n test
>   CI: enable t1509 in Travis and GitHub Actions
>
>  ci/lib.sh                 | 13 +++++++++++++
>  ci/run-docker-build.sh    |  3 +++
>  t/t1509-root-work-tree.sh |  4 ++--
>  3 files changed, 18 insertions(+), 2 deletions(-)

      parent reply	other threads:[~2020-05-13 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 13:23 [PATCH 0/2] CI: Enable t1509 on GitHub Actions and Travis Đoàn Trần Công Danh
2020-05-13 13:23 ` [PATCH 1/2] t1509: correct i18n test Đoàn Trần Công Danh
2020-05-13 16:43   ` Junio C Hamano
2020-05-13 13:23 ` [PATCH 2/2] CI: enable t1509 in Travis and GitHub Actions Đoàn Trần Công Danh
2020-05-13 16:51   ` Junio C Hamano
2020-05-13 23:52     ` Đoàn Trần Công Danh
2020-05-13 23:59       ` Junio C Hamano
2020-05-13 16:41 ` 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=xmqqh7wjvlbm.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=congdanhqx@gmail.com \
    --cc=git@vger.kernel.org \
    /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).