aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Muré <michael.mure@consensys.net>2019-10-12 13:43:44 +0900
committerGitHub <noreply@github.com>2019-10-12 13:43:44 +0900
commitcdfae4807db26a95fb55cb112b28b5975288b0e9 (patch)
treeb7210a51761061f6599aa8f0a5993c4f3d7b751f
parentbdb9c15a5e810c58b7dd960afd0b7645cfdc293b (diff)
parent6a8a172ef0f3b2f8da945d48355e1fc073aca755 (diff)
downloadgit-bug-cdfae4807db26a95fb55cb112b28b5975288b0e9.tar.gz
Merge pull request #225 from hoijui/patch-2
Model: reference git internals documentation
-rw-r--r--doc/model.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/model.md b/doc/model.md
index 79c6980e..ad5e6ce9 100644
--- a/doc/model.md
+++ b/doc/model.md
@@ -1,5 +1,7 @@
# Data model
+If you are not familiar with [git internals](https://git-scm.com/book/en/v1/Git-Internals), you might first want to read about them, as the `git-bug` data model is built on top of them.
+
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