@@ -11,14 +11,14 @@ equivalent to creating a new commit with the edited content and discarding the
11
11
old one. Hence, if a reply already exists on the old commit, it will not be
12
12
removed and the reply will still refer to the old commit. However, we do not
13
13
consider this restriction sever, especially when compared to mailing-lists,
14
- which inhibit the same restriction. Note that we currently still lack an tool
14
+ which inhibit the same restriction. Note that we currently still lack a tool
15
15
for convenient amending of messages.
16
16
17
17
18
18
## Issue notification/access control
19
19
20
20
Issues and related messages have to be pulled by the maintainer from public
21
- repositories. Otherwise issue reporters would require push access to the bug
21
+ repositories. Otherwise, issue reporters would require push access to the bug
22
22
repository. Originally, we planned (and still do plan) to provide a tool for
23
23
automated imports of issues and patches from mailing lists. A bug repository
24
24
may also be accessed via a web front-end at some point.
@@ -28,7 +28,7 @@ cross-platform notification of events in git repositories (e.g. pushes).
28
28
Using such a mechanism, contributors could notify a project maintainer about
29
29
changes in their public repositories, including issues or messages, via a public
30
30
API. A maintainer could set up automated fetches of new issues, importing new
31
- issues and messages. This is, however unrelated and still work in progress.
31
+ issues and messages. However, this is unrelated and still work in progress.
32
32
Additionally, it would still require reporters of issues to expose them via a
33
33
public repository.
34
34
0 commit comments