summaryrefslogtreecommitdiff
path: root/README.md
Commit message (Collapse)AuthorAgeFilesLines
* Fix spaces before tabs in indentationFrancois-Xavier Le Bail2023-02-151-1/+1
|
* Do not suggest patching Ultrix in README.md. [skip ci]Denis Ovsienko2022-07-061-3/+1
| | | | See commit 1fc034d and tcpdump-htdocs commit e7b1676.
* README.md: indicate that Solaris 11 also provides BPF. [skip ci]Guy Harris2022-03-241-5/+5
|
* Lose the CI badges in README.md. [skip ci]Denis Ovsienko2021-05-121-3/+0
| | | | See tcpdump commit e3a00d3 for the rationale.
* Rename a file back after commit 82001f3. [skip ci]Denis Ovsienko2021-02-051-1/+1
| | | | | | README.linux is a plain text file, rendering it as Markdown produces unreadable results. When and if someone converts it to a proper Markdown, it will be appropriate to rename the file again.
* Refine Markdown in README.md. [skip appveyor]Denis Ovsienko2021-01-281-38/+26
| | | | | | | | | | | | | | | | Move "by TTG" to the main header. Switch from the alternative headings format, which allows for H1 and H2 only, to the main one, which allows for H1 through H6. Have two H3 headers in the text. Fix CI badges to point to libpcap instead of tcpdump, and to use .com URLs for Travis CI. Make the security note bold to help more people actually get it. Add and improve hyperlink formatting in a few places. Fence the "from LBL" boilerplate and move it to the bottom of the first section. Make the "NOT", which was bold in commit 4a0b801, but didn't survive the initial Markdownization attempt in commit 82001f3, bold again. Escape filenames and sonames properly. Skip only some CI on this occasion, so Travis CI can transfer the build history from travis-ci.org to travus-ci.com and complete the migration.
* spell CONTRIBUTING.md (fixup commit 82001f3)Denis Ovsienko2020-01-101-1/+1
| | | | [skip ci]
* Add build status indicators, as per tcpdump.Guy Harris2019-10-291-0/+4
| | | | [skip ci]
* A bit more Markdowning; shuffle some stuff around, too.Guy Harris2019-10-291-12/+11
| | | | [skip ci]
* Use two-space indents for URLs separated from the surrounding text.Guy Harris2019-10-281-1/+2
| | | | | | The two spaces separate it from the text if you read the file as plain text, and it doesn't cause the URL to be displayed as raw non-link fixed-width text when it's formatte as Markdown.
* The answer is "nothing in Markdown, but it is now indented".Guy Harris2019-10-281-3/+3
| | | | | | Use it for all the separated URLs; that makes it look reasonable if you treat the file as human-readable plain text, and doesn't mess things up if it's formatted as Markdown.
* OK, just for fun, what does a three-space indent do?Guy Harris2019-10-281-1/+1
|
* Or omit the autolinking entirely.Guy Harris2019-10-281-8/+4
| | | | | Also, get rid of the FTP link to the USENIX paper, as 1) Markdown won't treat ftp: URLs as URLs and 2) that link is broken anyway.
* OK, try autolinks.Guy Harris2019-10-281-6/+6
|
* Try to handle URL paragraphs better.Guy Harris2019-10-281-6/+6
| | | | | | | We'd like this document to show links as links when formatted as Markdown *and* to have it be at least somewhat readable as plain text, so we want to have the URLs set off somewhat for the latter. Try block quoting.
* Indent isolated URLs with spaces, not tabs.Guy Harris2019-10-281-5/+5
| | | | | Markdown will show them as fixed-width un-clickable text if indented with tabs, but will show them as indented links if indented with spaces.
* rename/reformat documentation to markdownlibpcap-1.9-bpMichael Richardson2018-06-241-0/+93
View Lorry Controller Status