| Age | Commit message (Collapse) | Author |
|---|
|
o echo_example_usage
needed to escape some backslashes in an inner quote
o find_full_usage
missing a \n at the end of the -name line
? getopt_full_usage
the -o line has tab issues, but I didn't fix them.
o length_example_usage
removed some double-quotes that were within an inner quotes
o printf_example_usage
needed to escape a backslash in an inner quote
o sort_example_usage
needed to escape some backslashes and double quotes in an inner quote
o tftp_full_usage
s/nameing/naming/;
o umount_full_usage
remove colons after options for consistency w/ other full_usage messages
o uniq_example_usage
needed to escape some backslashes and double quotes in an inner quote
- TODO xargs -l ?
- docs/autodocifier.pl POD && comment updates
- docs/busybox_footer.pod added Larry Doolittle and Sterling Huxley
|
|
|
|
announcement for it on the main page.
|
|
-Erik
|
|
wget HTTP 1.1 support and addes chunked encoding so bb wget
is now fully RFC compliant.
|
|
|
|
|
|
-Erik
|
|
- support for ftp downloads
- HTTP basic authentication support (as an optional feature)
- handling of http redirections
- protocol version changed to 1.0 (to stop servers from requesting
chunked encoding)
- bugfix: in the case when content-length not given, wget didn't
download anything
- when attempting to continue an aborted download but server doesn't
support restarts, reopen output file in write mode
- changed assumption that existing file should restart an aborted
download. Now the user must explicitly specify this with -c
|
|
is handled correctly.
|
|
the body will be generated by docs/autodocifier.pl
|
|
|
|
you can specify an arbitrary behavior for 'ctrlaltdel' without that behavior
needing to be a reboot.
|
|
|
|
|
|
need", example of a testcase, more janitorial items, and a whole new section
with guidelines on committing changes to CVS.
|
|
linkes to a Wired article on Midori Linux.
|
|
|
|
|
|
|
|
- updated autodocifier.pl to use tab to indent example section
|
|
|
|
Fix up docs/busybox.pod with the latest autogenerated output.
-Erik
|
|
mk2knr.pl script. Also some minor cleanups.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
line appears at the bottom instead of the top. The
indentation semantics of POD make the first item in
the (=over,=back) block look weird the other way.
- implemented a way to encode example usage into usage.h
One would define a macro called "${applet}_example_usage"
which would expand to the example text.
- The example usage is considered optional, but trivial and
full usage are not.
Here's an example using chown.
---- before
#define chown_trivial_usage \
"[OPTION]... OWNER[<.|:>[GROUP] FILE..."
#define chown_full_usage \
"Change the owner and/or group of each FILE to OWNER and/or GROUP.\n" \
"\nOptions:\n" \
"\t-R\tChanges files and directories recursively."
#define chown_example_usage \
"\t$ ls -l /tmp/foo\n" \
"\t-r--r--r-- 1 andersen andersen 0 Apr 12 18:25 /tmp/foo\n" \
"\t$ chown root /tmp/foo\n" \
"\t$ ls -l /tmp/foo\n" \
"\t-r--r--r-- 1 root andersen 0 Apr 12 18:25 /tmp/foo\n" \
"\t$ chown root.root /tmp/foo\n" \
"\tls -l /tmp/foo\n" \
"\t-r--r--r-- 1 root root 0 Apr 12 18:25 /tmp/foo\n"
---- after
=item I<chown>
chown [OPTION]... OWNER[<.|:>[GROUP] FILE...
Change the owner and/or group of each FILE to OWNER and/or GROUP.
Options:
-R Changes files and directories recursively.
Example:
$ ls -l /tmp/foo
-r--r--r-- 1 andersen andersen 0 Apr 12 18:25 /tmp/foo
$ chown root /tmp/foo
$ ls -l /tmp/foo
-r--r--r-- 1 root andersen 0 Apr 12 18:25 /tmp/foo
$ chown root.root /tmp/foo
ls -l /tmp/foo
-r--r--r-- 1 root root 0 Apr 12 18:25 /tmp/foo
-------------------------------
|
|
|
|
|
|
|
|
pod_from_usage() is the default generator.
|
|
that were intended to be indented.
|
|
|
|
more robustly. I also blow away any USAGE_NOT_\w+ macros.
|
|
|
|
|
|
* make headers and footers for both the POD and SGML content
* make an SGML generator
* finish the command-line handling
Also, some of the documentation in usage.h will have to
be adjusted. expr needs some lines to be indented, and
ls has a stray comma. I may have missed some things...
but it looks OK for the most part.
|
|
|
|
will be used (when it works) to autogenerate documentation. Based on
code written by Mark Whitley.
|
|
|
|
|
|
|
|
|
|
|
