From: Alex Riesen <raa.lkml@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
"René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Subject: Re: [PATCH] Use find instead of perl in t5000 to get file modification time
Date: Thu, 30 Oct 2008 08:26:10 +0100 [thread overview]
Message-ID: <20081030072610.GA1052@steel.home> (raw)
In-Reply-To: <20081029215444.GA19874@sigill.intra.peff.net>
Jeff King, Wed, Oct 29, 2008 22:54:45 +0100:
> On Wed, Oct 29, 2008 at 11:38:32AM +0100, Alex Riesen wrote:
>
> > There can be a problem with "-printf": Open Group SUS does not specify
> > -printf for find(1), so it is probably a problem somewhere. I just don't know.
> > [...]
> > + find extract/a/a -printf "%T@\\n" >b.mtime &&
>
> $ uname -sr
> FreeBSD 6.1-RELEASE-p17-jc1
> $ find . -printf "%T@\\n"
> find: -printf: unknown option
>
> > There is always a fallback, which is to write a small program which calls
> > native stat(2). Or modify test-chmtime to just print mtime when asked.
>
> I think that makes the most sense.
>
Ok, will do.
next prev parent reply other threads:[~2008-10-30 7:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 10:38 [PATCH] Use find instead of perl in t5000 to get file modification time Alex Riesen
2008-10-29 21:54 ` Jeff King
2008-10-30 7:26 ` Alex Riesen [this message]
2008-10-30 5:29 ` Sam Vilain
2008-10-31 7:00 ` Alex Riesen
2008-10-31 12:59 ` Peter Harris
2008-10-31 13:45 ` Alex Riesen
2008-10-31 22:14 ` Johannes Schindelin
2008-10-31 23:37 ` Alex Riesen
2008-11-01 0:23 ` Johannes Schindelin
2008-11-01 14:24 ` Alex Riesen
2008-11-01 20:37 ` Johannes Schindelin
2008-11-02 14:37 ` Alex Riesen
2008-11-02 16:05 ` Johannes Schindelin
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=20081030072610.GA1052@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).