From: Alex Elder <aelder@sgi.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH 0/3, v2] ltp: eliminate more build warnings
Date: Mon, 11 Apr 2011 13:31:36 -0500 [thread overview]
Message-ID: <1302546696.2580.25.camel@doink> (raw)
I think I have addressed the concerns raised by
Garrett Cooper for the following three patches.
My original intent was to provide fairly simple
fixes to these build warnings. This code appears
to be quite old and could really benefit from a
some more comprehensive updating, but that is
well beyond the scope of what I'm trying to do.
Nevertheless, Garrett's suggestions were quite
valid so I did what I could to address them.
-Alex
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2011-04-11 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 18:31 Alex Elder [this message]
2011-04-12 6:14 ` [LTP] [PATCH 0/3, v2] ltp: eliminate more build warnings Garrett Cooper
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=1302546696.2580.25.camel@doink \
--to=aelder@sgi.com \
--cc=ltp-list@lists.sourceforge.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