Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
K
kernel
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
redox-os
kernel
Commits
0ae08c52
Commit
0ae08c52
authored
8 years ago
by
Adam Niederer
Committed by
GitHub
8 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Fix spelling & grammar in README.md
parent
78171226
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!7
Fix spelling & grammar in README.md
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+4
-4
4 additions, 4 deletions
README.md
with
4 additions
and
4 deletions
README.md
+
4
−
4
View file @
0ae08c52
...
...
@@ -26,7 +26,7 @@ careful comments for anything non-trivial.
## Guidelines
### A rotten house is built on a rotten funda
ment
.
### A rotten house is built on a rotten f
o
unda
tion
.
Don't fool yourself. You are likely not getting back to the ugly code. Write it
the right way
**first time**
, and make sure you only move on when it's
...
...
@@ -45,7 +45,7 @@ Every public item should contain API documentation.
Abusing debug assertions is a wonderful way to catch bugs, and it is very much
encouraged.
### Static
al
checking
### Static checking
Rust provides a lot of type-system features which can be used to create
wonderful safe abstractions, and you should use them whenever you get the chance.
...
...
@@ -65,5 +65,5 @@ and be careful.
### Commits
Use descriptive commits. One way to force yourself to do that is to not pass the
`-m`
flag, which will make your editor pop up, so
that
you can conv
i
niently
write long
commit messages.
`-m`
flag, which will make your editor pop up, so you can conv
e
niently
write long
commit messages.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment