Favicon #30
Merged
Favicon #30
Conversation
This file contains 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
|
maybe merge ? alternatively I can simplify it to the option I mentioned above. I actually started thinking that favicon is not that necessary for such a project and does not justify added dependencies :) But, need an opinion :) |
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.
to #29
This one appeared to be a bit messy. At the end I started looking into this option - meaning just ignore favicon requests. Maybe ... it is simpler to remove the favicon and choose that way ?
So:
publicin the root./builddir, not./build/src- this is for good anyway. But ended up messing the PR a bit, sorry for this.