From: Junio C Hamano <gitster@pobox.com>
To: Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t/helper: 'test-chmtime (--get|-g)' to print only the mtime
Date: Mon, 09 Apr 2018 12:29:12 +0900 [thread overview]
Message-ID: <xmqqvad15a7r.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180406221947.28402-1-ungureanupaulsebastian@gmail.com> (Paul-Sebastian Ungureanu's message of "Sat, 7 Apr 2018 01:19:47 +0300")
Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com> writes:
> - find .git/rr-cache/ -type f | xargs test-chmtime -172800 &&
> + test-chmtime -172800 $(find .git/rr-cache/ -type f) &&
You've sneaked this kind of rewrite in, as if you are testing to see
how careful the reviewers are ;-).
We often use "find piped to xargs" pattern to avoid unbounded number
of paths from appearing on a command line, busting platform limits.
In the case of these test scripts, it does not matter very much, but
such a "we can save a process and a pipe this way" optimization is
not within the scope of "chmtime +v often is piped to sed only to
strip path---let's give it a way to just grab the timestamp" topic.
Not a very welcome change.
Having said that, I do not want this to be rerolled if this
unrelated "removal of find-piped-to-xargs pattern" is the only
niggle in the patch, as I've already checked if these conversions
are safe (they are---we are not dealing with hundreds of stuff in
.git/objects/ or .git/rr-cache/). There were conflicts caused by
this patch and nd/combined-test-helper (which makes the test-chmtime
standalone binary as a subcommand of test-tool); I think I resolved
them correctly, but please double check when I update the public
repositories in several hours.
Thanks.
prev parent reply other threads:[~2018-04-09 3:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 22:19 [PATCH] t/helper: 'test-chmtime (--get|-g)' to print only the mtime Paul-Sebastian Ungureanu
2018-04-09 2:35 ` Junio C Hamano
2018-04-09 3:29 ` 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=xmqqvad15a7r.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ungureanupaulsebastian@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 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).