git-tickets

commit

d022dad14f831d37dcad98bbe45a3694f413ddf9

parent

268cd35ec904265d562dbb4cfe3452d9f8989522

Author

Tobias Bengfort <tobias.bengfort@posteo.de>

Date

2017-07-16 17:35

typos

Diffstat

1 files changed, 8 insertions, 7 deletions

diff --git a/README.md b/README.md

@@ -104,7 +104,7 @@ Also note that any changes can be tracked in the git history.
  104   104 
  105   105 ### How can I edit code and tickets at the same time.
  106   106 
  107    -1 This is a clear disadvantage of this approach: You can not easily switch
   -1   107 This is a clear disadvantage of this approach: You cannot easily switch
  108   108 between regular code and the "tickets" branch. You can have a second clone of
  109   109 the repo though.
  110   110 
@@ -129,13 +129,14 @@ deal with HTML-email, MIME, encryption, different encodings, ….
  129   129 ### Why are there no threaded discussions? Even github has them!
  130   130 
  131   131 Github does not have threaded discussions in general. However, you can comment
  132    -1 code lines in pull requests, which results in somthing very similar to threads.
   -1   132 code lines in pull requests, which results in something very similar to
   -1   133 threads.
  133   134 
  134   135 Unfortunately, it is quite hard to represent threads in a human readable plain
  135    -1 text file. You may use the `In-Reply-To` header, but I belive that extensive
   -1   136 text file. You may use the `In-Reply-To` header, but I believe that extensive
  136   137 quoting should be sufficient for most cases.
  137   138 
  138    -1 ### When the zombie apocalypse starts and the github engineers are among the first victims (god behold!) and github goes down imidiately, will this be our saviour?
   -1   139 ### When the zombie apocalypse starts and the github engineers are among the first victims (god behold!) and github goes down immediately, will this be our saviour?
  139   140 
  140   141 Yes.
  141   142 
@@ -147,8 +148,8 @@ there are some key differences:
  147   148 -	[github] is much more than a ticket system and offers (among other things)
  148   149 	hosting, a web interface, permission management, and project discovery.
  149   150 -	A web interface is used instead of editing plain text files.
  150    -1 -	A seperate authentication system is used.
  151    -1 -	Github is a single point of failure. You can not easily migrate to another
   -1   151 -	A separate authentication system is used.
   -1   152 -	Github is a single point of failure. You cannot easily migrate to another
  152   153 	hoster.
  153   154 
  154   155 ### How does git-tickets compare to mailing lists?
@@ -162,7 +163,7 @@ free-text communication. But there are some important differences:
  162   163 
  163   164 -	No ticket-specific filters.
  164   165 -	Tools do not implicitly know about the code that is discussed.
  165    -1 -	A seperate authentication system is used.
   -1   166 -	A separate authentication system is used.
  166   167 -	A separate server is needed.
  167   168 
  168   169 ### How does git-tickets compare to mailing debbugs?