From: Junio C Hamano <gitster@pobox.com>
To: Mike Gorchak <mike.gorchak.qnx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/1] Fix unsigned time_t comparison
Date: Mon, 25 Feb 2013 14:10:56 -0800 [thread overview]
Message-ID: <7vvc9gnixb.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAHXAxrMZODO07_dPep-yKgrzD1228iSMGUXX06xkKDmoZF4+qA@mail.gmail.com> (Mike Gorchak's message of "Mon, 25 Feb 2013 23:51:16 +0200")
Mike Gorchak <mike.gorchak.qnx@gmail.com> writes:
> Do not compare time_t (less comparison) with -1. If time_t
> is unsigned this leads to always true comparison.
>
> Signed-off-by: Mike Gorchak <mike.gorchak.qnx@gmail.com>
> ---
> date.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/date.c b/date.c
> index 57331ed..1ac28e5 100644
> --- a/date.c
> +++ b/date.c
> @@ -383,7 +383,7 @@ static int is_date(int year, int month, int day,
> struct tm *now_tm, time_t now,
> * sense to specify timestamp way into the future. Make
> * sure it is not later than ten days from now...
> */
> - if (now + 10*24*3600 < specified)
> + if ((specified != -1) && (now + 10*24*3600 < specified))
> return 0;
> tm->tm_mon = r->tm_mon;
> tm->tm_mday = r->tm_mday;
This is good enough band-aid for now (as it won't change the
semantics for anybody), but I suspect in the longer term we would
want to pick a different mechanims to signal errors, so that we can
specify timestamp that is before 1970.
Thanks, will queue.
next prev parent reply other threads:[~2013-02-25 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 21:51 [PATCH 1/1] Fix unsigned time_t comparison Mike Gorchak
2013-02-25 22:10 ` Junio C Hamano [this message]
2013-02-25 22:27 ` 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=7vvc9gnixb.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mike.gorchak.qnx@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