From 6a8a172ef0f3b2f8da945d48355e1fc073aca755 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20Mur=C3=A9?= Date: Sat, 12 Oct 2019 13:43:30 +0900 Subject: [PATCH] Update model.md --- doc/model.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/model.md b/doc/model.md index 03d9c65c4b929d38954a35bf13db26eb711364ba..8d0bdde87206aba910f270cabf934bc5e4f1a12a 100644 --- a/doc/model.md +++ b/doc/model.md @@ -1,8 +1,6 @@ # 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. +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.