mirror of
https://github.com/curl/curl.git
synced 2026-04-15 01:01:41 +03:00
GHA/checkdocs: re-enable proselint, update setup, fix issues found
- update configuration and invocation.
- install via pip.
- drop a file exception.
- alpha sort proselint settings.
- FILEFORMAT: update text about XML compliance.
- CI job takes 22 seconds total.
Ref: https://github.com/amperser/proselint/releases/tag/v0.16.0
Follow-up to 38bfe1c2aa #15314
Closes #19931
This commit is contained in:
parent
8ff5222b4e
commit
46429d6f44
10 changed files with 68 additions and 67 deletions
|
|
@ -317,7 +317,7 @@ See this [list of public HTTP/3 servers](https://bagder.github.io/HTTP3-test/)
|
|||
### HTTPS eyeballing
|
||||
|
||||
With option `--http3` curl attempts earlier HTTP versions as well should the
|
||||
connect attempt via HTTP/3 not succeed "fast enough". This strategy is similar
|
||||
connect attempt via HTTP/3 fail "fast enough". This strategy is similar
|
||||
to IPv4/6 happy eyeballing where the alternate address family is used in
|
||||
parallel after a short delay.
|
||||
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ account.
|
|||
|
||||
We regularly run our code through the [Coverity static code
|
||||
analyzer](https://scan.coverity.com/) thanks to them offering this service to
|
||||
us for free.
|
||||
us free of charge.
|
||||
|
||||
## CodeSonar
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ domain names, including `curl.se` and `curl.dev`. Daniel Stenberg owns these
|
|||
domain names.
|
||||
|
||||
Until a few years ago, the curl website was present at `curl.haxx.se`. The
|
||||
`haxx.se` domain is owned by Haxx AB, administrated by Daniel Stenberg. The
|
||||
`haxx.se` domain is owned by Haxx AB, administered by Daniel Stenberg. The
|
||||
curl.haxx.se name is meant to keep working and be redirecting to curl.se for
|
||||
the foreseeable future.
|
||||
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@ text file:
|
|||
curl -F '=(;type=multipart/alternative' \
|
||||
-F '=plain text message' \
|
||||
-F '= <body>HTML message</body>;type=text/html' \
|
||||
-F '=)' -F '=@textfile.txt' ... smtp://example.com
|
||||
-F '=)' -F '=@textfile.txt' ... smtp://example.com
|
||||
|
||||
Data can be encoded for transfer using encoder=. Available encodings are
|
||||
*binary* and *8bit* that do nothing else than adding the corresponding
|
||||
|
|
|
|||
|
|
@ -28,8 +28,7 @@ different levels of encryption required.
|
|||
This option is handled in LDAP (added in 7.81.0). It is fully supported by the
|
||||
OpenLDAP backend and ignored by the generic ldap backend.
|
||||
|
||||
Please note that a server may close the connection if the negotiation does
|
||||
not succeed.
|
||||
Please note that a server may close the connection if the negotiation fails.
|
||||
|
||||
This option was formerly known as --ftp-ssl (added in 7.11.0). That option
|
||||
name can still be used but might be removed in a future version.
|
||||
|
|
|
|||
|
|
@ -21,5 +21,5 @@ specified as either a single flag value or a comma-separated list
|
|||
of flag values. These values are case-sensitive and may be negated
|
||||
by prepending them with a '-' character. Currently the following
|
||||
flag values are accepted: answered, deleted, draft, flagged, and
|
||||
seen. The currently-accepted flag values are used to set flags on
|
||||
seen. The currently accepted flag values are used to set flags on
|
||||
IMAP uploads.
|
||||
|
|
|
|||
|
|
@ -24,8 +24,8 @@ need to copy the style already used in the source code and there are no
|
|||
particularly unusual rules in our set of rules.
|
||||
|
||||
We also work hard on writing code that are warning-free on all the major
|
||||
platforms and in general on as many platforms as possible. Code that obviously
|
||||
causes warnings is not accepted as-is.
|
||||
platforms and in general on as many platforms as possible. Code that causes
|
||||
warnings is not accepted as-is.
|
||||
|
||||
## Readability
|
||||
|
||||
|
|
|
|||
|
|
@ -45,7 +45,7 @@ do not attempt to use SSL.
|
|||
## CURLUSESSL_TRY
|
||||
|
||||
Try using SSL, proceed as normal otherwise. Note that server may close the
|
||||
connection if the negotiation does not succeed.
|
||||
connection if the negotiation fails.
|
||||
|
||||
## CURLUSESSL_CONTROL
|
||||
|
||||
|
|
|
|||
|
|
@ -11,10 +11,9 @@ XML. All data for a single test case resides in a single ASCII file. Labels
|
|||
mark the beginning and the end of all sections, and each label must be written
|
||||
in its own line. Comments are either XML-style (enclosed with `<!--` and
|
||||
`-->`) or shell script style (beginning with `#`) and must appear on their own
|
||||
lines and not alongside actual test data. Most test data files are
|
||||
syntactically-valid XML (a few files are not); lack of support for character
|
||||
entities is a big difference but macros like %CR fill that particular role
|
||||
here.
|
||||
lines and not alongside actual test data. Test data files are syntactically
|
||||
valid XML; lack of support for character entities is a big difference but macros
|
||||
like %CR fill that particular role here.
|
||||
|
||||
Each test case source exists as a file matching the format
|
||||
`tests/data/testNUM`, where `NUM` is the unique test number, and must begin
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue