From: Chris Rorvick <chris@rorvick.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-cvsimport: allow author-specific timezones
Date: Mon, 15 Oct 2012 21:26:05 -0500 [thread overview]
Message-ID: <CAEUsAPY3fJJSzX8WPRVQPNOF0A0KAMCXr1u0ZzjEFvXDF=v6JA@mail.gmail.com> (raw)
In-Reply-To: <7vpq4jws4d.fsf@alter.siamese.dyndns.org>
On Mon, Oct 15, 2012 at 12:40 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> diff --git a/t/t9604-cvsimport-timestamps.sh b/t/t9604-cvsimport-timestamps.sh
>> new file mode 100644
>
> Huh? What happened to the executable bit we saw earlier?
Uh, yeah. Sorry about that.
>> +test_expect_success 'check timestamps are UTC (TZ=Australia/Sydney)' '
>> +
>> + TZ=America/Chicago git cvsimport -p"-x" -C module-2 module &&
>
> This look identical to the first one, but even with a trivial change
> to use Australia/Sydney instead of Chicago, I am not sure what the
> test buys us.
This is left over from when I was using the script to test the "use
local timezone" option. It was useless there, too, but did provide
some symmetry. :-) Removed.
It occurred to me that the success of the unit test depends on the
host platform's zoneinfo database. I think this problem is inherent
with this functionality. Should the unit test attempt to detect
support for the used timezones and short circuit if this fails? Not
sure exactly how I'd do this, but wondering if it's worth thinking
about.
I've made all the other recommended changes, I'll resubmit shortly.
Thanks,
Chris
next prev parent reply other threads:[~2012-10-16 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 0:30 [PATCH] git-cvsimport: allow author-specific timezones Chris Rorvick
2012-10-15 17:40 ` Junio C Hamano
2012-10-16 2:26 ` Chris Rorvick [this message]
2012-10-16 3:50 ` Junio C Hamano
2012-10-16 6:31 ` Jeff King
2012-10-16 15:49 ` Junio C Hamano
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='CAEUsAPY3fJJSzX8WPRVQPNOF0A0KAMCXr1u0ZzjEFvXDF=v6JA@mail.gmail.com' \
--to=chris@rorvick.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).