From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 0/9] misc. cleanups
Date: Tue, 6 Mar 2007 20:44:04 -0500 [thread overview]
Message-ID: <20070307014403.GA26482@spearce.org> (raw)
This is a series of various cleanups that I have pending at the
front of my pack v4 topic. The earlier ones are annoying nits,
the later ones fix compiler errors caused by compiling with:
--snip--
CFLAGS += -Wall -ansi -pedantic -std=c99
ifdef strict
CFLAGS += -Werror
CFLAGS += -Wfour-char-constants
CFLAGS += -fnon-lvalue-assign
CFLAGS += -Wdeclaration-after-statement
CFLAGS += -Wpointer-arith
CFLAGS += -Wbad-function-cast
CFLAGS += -Wcast-align
CFLAGS += -Wwrite-strings
CFLAGS += -Wshorten-64-to-32
# No, currently a huge set.
#CFLAGS += -Wsign-compare
# No, only in diffcore-rename and that's ok.
#CFLAGS += -Wfloat-equal
# No, unused parameters, -Wsign-compare, missing initializers.
# CFLAGS += -Wextra
# No, memcmp trips on signed/unsigned conversion.
# CFLAGS += -Wconversion
endif
--snap--
--
Shawn.
reply other threads:[~2007-03-07 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070307014403.GA26482@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).