MichaelMure/git-bug
1
1
Fork 0
mirror of https://github.com/MichaelMure/git-bug.git synced 2024-12-14 08:45:30 +03:00
Code Issues Projects Releases Wiki Activity

docs: fix some typos

Browse Source
This commit is contained in:
Zetok Zalbavar 2018-08-17 18:44:38 +01:00
parent c974cc022d
commit 73bd0f4a4e
No known key found for this signature in database
GPG Key ID: C953D3880212068A
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -9,11 +9,11 @@
Would it be nice to not have to rely on a web service somewhere to deal with bugs ?
Would it be nice to be able to browse and edit bug report offline ?
Would it be nice to be able to browse and edit bug reports offline?
`git-bug` is a distributed bug tracker embedded in `git`. It use git's internal storage so **no files are added in your project**.
`git-bug` is a distributed bug tracker embedded in `git`. It uses git's internal storage so **no files are added in your project**.
As you would do with commits and branches, you can push your bugs to the same git remote your are already using to collaborate with other peoples.
As you would do with commits and branches, you can push your bugs to the same git remote you are already using to collaborate with other people.
:construction: This is for now a proof of concept. Expect dragons and unfinished business. :construction:

4
doc/model.md
View File

@ -1,6 +1,6 @@
# Data model
The biggest problem when creating a distributed bug tracker is that there is no central authoritative server (doh!). This imply some constraint.
The biggest problem when creating a distributed bug tracker is that there is no central authoritative server (doh!). This implies some constraints.
## Anybody can create and edit bugs at the same time as you
@ -97,4 +97,4 @@ Example of Tree of a later commit of a bug:
100644 blob 68383346c1a9503f28eec888efd300e9fc179ca0 ops
100644 blob a020a85baa788e12699a4d83dd735578f0d78c75 root
```
Note that the `"root"` entry still reference the same root OperationPack. Also, all the clocks reference the same empty `Blob`.
Note that the `"root"` entry still reference the same root OperationPack. Also, all the clocks reference the same empty `Blob`.