From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: Fix big left-shifts of unsigned char
Date: Thu, 18 Jun 2009 01:21:52 -0700 [thread overview]
Message-ID: <7vbpomymsf.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0906181012050.4848@intel-tinevez-2-302> (Johannes Schindelin's message of "Thu\, 18 Jun 2009 10\:12\:37 +0200 \(CEST\)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Wed, 17 Jun 2009, Linus Torvalds wrote:
>
>> This is _not_ tested in any way. And I got bored with getting rid of
>> 'unsigned char' variables, so I by no means did all of them, just the
>> first few that caugth my grepping eye.
>
> I wonder if there is a mode of 'sparse' which could spot these buggers.
That's a very good meta question ;-)
next prev parent reply other threads:[~2009-06-18 8:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 20:03 [PATCH] Cast things properly to handle >2G files Alfred M. Szmidt
2009-06-14 20:17 ` Johannes Schindelin
2009-06-15 2:43 ` Nicolas Pitre
2009-06-15 3:39 ` Alfred M. Szmidt
2009-06-15 4:06 ` Junio C Hamano
2009-06-15 8:45 ` Johannes Schindelin
2009-06-15 4:25 ` Linus Torvalds
2009-06-17 22:27 ` Alfred M. Szmidt
2009-06-17 22:45 ` Linus Torvalds
2009-06-17 23:16 ` Junio C Hamano
2009-06-18 0:22 ` Fix big left-shifts of unsigned char Linus Torvalds
2009-06-18 8:12 ` Johannes Schindelin
2009-06-18 8:21 ` Junio C Hamano [this message]
2009-06-18 16:08 ` Linus Torvalds
2009-06-18 16:45 ` Johannes Schindelin
2009-06-18 17:15 ` Linus Torvalds
2009-06-18 17:28 ` Fix various sparse warnings in the git source code Linus Torvalds
2009-06-18 17:45 ` Matthieu Moy
2009-06-18 17:52 ` Linus Torvalds
2009-06-18 21:48 ` Linus Torvalds
2009-06-17 22:51 ` [PATCH] Cast things properly to handle >2G files Linus Torvalds
2009-06-17 22:27 ` Alfred M. Szmidt
2009-06-17 22:48 ` Linus Torvalds
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=7vbpomymsf.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.