All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Han-Wen Nienhuys <hanwenn@gmail.com>
Subject: Re: [PATCH 0/2] fix 2 more test files that were accessing file system directly.
Date: Tue, 06 Jul 2021 12:55:56 -0700	[thread overview]
Message-ID: <xmqqk0m3i5df.fsf@gitster.g> (raw)
In-Reply-To: <pull.1042.git.git.1625597277.gitgitgadget@gmail.com> (Han-Wen Nienhuys via GitGitGadget's message of "Tue, 06 Jul 2021 18:47:55 +0000")

"Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com> writes:

> This reduced the number of test failures in the reftable series by a bit.
>
> Han-Wen Nienhuys (2):
>   t1415: avoid direct filesystem access for writing refs
>   t7509: avoid direct file access for writing CHERRY_PICK_HEAD

Thanks.  Both look quite sensible.

Will queue.


>
>  t/t1415-worktree-refs.sh     | 10 ++++------
>  t/t7509-commit-authorship.sh |  4 ++--
>  2 files changed, 6 insertions(+), 8 deletions(-)
>
>
> base-commit: 670b81a890388c60b7032a4f5b879f2ece8c4558
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1042%2Fhanwen%2Freftable-tests2-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1042/hanwen/reftable-tests2-v1
> Pull-Request: https://github.com/git/git/pull/1042

      parent reply	other threads:[~2021-07-06 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06 18:47 [PATCH 0/2] fix 2 more test files that were accessing file system directly Han-Wen Nienhuys via GitGitGadget
2021-07-06 18:47 ` [PATCH 1/2] t1415: avoid direct filesystem access for writing refs Han-Wen Nienhuys via GitGitGadget
2021-07-06 18:47 ` [PATCH 2/2] t7509: avoid direct file access for writing CHERRY_PICK_HEAD Han-Wen Nienhuys via GitGitGadget
2021-07-06 19:55 ` 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=xmqqk0m3i5df.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=hanwenn@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.