From: Art Haas <ahaas@airmail.net>
To: alsa-devel@lists.sourceforge.net
Subject: Patches for replacing obsolete GCC initializers
Date: Wed, 16 Jul 2003 13:57:13 -0500 [thread overview]
Message-ID: <20030716185713.GG671@artsapartment.org> (raw)
Hi.
I have a large set of patches removing the obsolete GCC structure
initializers and replacing them with C99 initializers. The total patch
set is around 70K and affects 34 files. Would it be acceptable to post
the patch in compressed form to the list, or would posting the patches
in say two or three sets be better?
Art Haas
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
next reply other threads:[~2003-07-16 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 18:57 Art Haas [this message]
2003-07-17 8:55 ` Patches for replacing obsolete GCC initializers Takashi Iwai
2003-07-17 12:37 ` Art Haas
2003-07-17 12:44 ` Takashi Iwai
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=20030716185713.GG671@artsapartment.org \
--to=ahaas@airmail.net \
--cc=alsa-devel@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 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.