readme: update #17
Open
readme: update #17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
illwieckz
force-pushed
the
illwieckz/readme
branch
from
9f50375 to
540e34f
Compare
|
This also removes a bunch of paragraphs that are specific to building the Google repo, and how to report bugs to Google, which don't apply there. |
illwieckz
force-pushed
the
illwieckz/readme
branch
3 times, most recently
from
8e8a1f3 to
042ddbe
Compare
|
Exemple of confusion people had when not being sure this was purposed for something else than MinGW:
From: |
|
Also by having an up-to-date README the project looks maintained (and it is). |
|
We may also include some knowledge discussed here: |
illwieckz
force-pushed
the
illwieckz/readme
branch
15 times, most recently
from
3700055 to
b05074e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some readme update.
First motivation was to remove the CI badges that are not ours and may be broken or outdated.
Then I added some rewording to make it better, for example the generic information about Breakpad with Google links is now under the “Upstream Breakpad” section, and the “Breakpad for MinGW and more” title removes the ambiguity that can lead to the wrong belief it is for MinGW exclusively.
I also marked as optional some instructions that aren't needed to build breakpad.