From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH setup 0/8] Remove cruft from setup
Date: Sun, 22 Jan 2017 14:16:00 -0000 [thread overview]
Message-ID: <20170122141623.226172-1-jon.turney@dronecode.org.uk> (raw)
Mainly this is cruft in the setup.ini parser, noticed while updating [1] to
align with source code.
[1] https://sourceware.org/cygwin-apps/setup.ini.html
Jon Turney (8):
Make package size and checksum mandatory in setup.ini
Remove unused lexer tokens
Remove parser rules which do nothing
Remove parser rules which store data which is never used.
Remove unused syntax for separate size and hash lines
Remove redundant parser rule
Remove unused cvsid
Remove an obsolete prototype
ConnectionSetting.cc | 5 --
FindVisitor.cc | 5 --
IniDBBuilder.h | 14 -----
IniDBBuilderPackage.cc | 145 ------------------------------------------------
IniDBBuilderPackage.h | 15 -----
IniParseFeedback.cc | 5 --
KeysSetting.cc | 5 --
LogFile.cc | 5 --
PackageSpecification.cc | 4 --
ScanFindVisitor.cc | 5 --
SourceSetting.cc | 5 --
archive.cc | 5 --
archive_tar.cc | 5 --
archive_tar_file.cc | 4 --
choose.cc | 5 --
crypto.cc | 5 --
cygpackage.cc | 5 --
desktop.cc | 5 --
dialog.cc | 5 --
diskfull.cc | 5 --
download.cc | 5 --
filemanip.cc | 5 --
find.cc | 5 --
geturl.cc | 5 --
gpg-packet.cc | 5 --
inilex.ll | 42 --------------
inilintmain.cc | 5 --
iniparse.yy | 72 ++++--------------------
install.cc | 4 --
io_stream.cc | 5 --
io_stream_cygfile.cc | 5 --
io_stream_file.cc | 5 --
io_stream_memory.cc | 5 --
main.cc | 5 --
mkdir.cc | 5 --
mklink2.cc | 5 --
mount.cc | 4 --
msg.cc | 5 --
net.cc | 5 --
netio.cc | 5 --
nio-file.cc | 5 --
nio-ftp.cc | 5 --
nio-http.cc | 5 --
nio-ie5.cc | 5 --
package_db.cc | 4 --
package_meta.cc | 5 --
package_meta.h | 13 +----
package_source.cc | 5 --
package_source.h | 13 +----
package_version.cc | 47 ----------------
package_version.h | 8 +--
postinstall.cc | 5 --
prereq.cc | 5 --
root.cc | 5 --
script.cc | 5 --
simpsock.cc | 5 --
site.cc | 5 --
source.cc | 5 --
state.cc | 5 --
win32.cc | 5 --
60 files changed, 15 insertions(+), 604 deletions(-)
--
2.8.3
next reply other threads:[~2017-01-22 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 14:16 Jon Turney [this message]
2017-01-22 14:16 ` [PATCH setup 1/8] Make package size and checksum mandatory in setup.ini Jon Turney
2017-01-22 14:17 ` [PATCH setup 6/8] Remove redundant parser rule Jon Turney
2017-01-22 14:17 ` [PATCH setup 2/8] Remove unused lexer tokens Jon Turney
2017-01-22 14:17 ` [PATCH setup 7/8] Remove unused cvsid Jon Turney
2017-01-22 14:17 ` [PATCH setup 3/8] Remove parser rules which do nothing Jon Turney
2017-01-22 14:17 ` [PATCH setup 4/8] Remove parser rules which store data which is never used Jon Turney
2017-01-22 14:17 ` [PATCH setup 5/8] Remove unused syntax for separate size and hash lines Jon Turney
2017-01-22 14:18 ` [PATCH setup 8/8] Remove an obsolete prototype Jon Turney
2017-01-23 10:37 ` [PATCH setup 0/8] Remove cruft from setup Corinna Vinschen
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=20170122141623.226172-1-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).