Correct issue in FAQ page to link to GitHub issue.

diff --git a/releases.moxie b/releases.moxie
index e0f9223e33ffc1fad7210405b6dc34b7e9ce0a8a..6bf7593f48966a4f23ac0052f8b6dbbe26586a70 100644 (file)
--- a/releases.moxie
+++ b/releases.moxie
@@ -6,7 +6,7 @@ r30: {
     id: ${project.version}
     date: ${project.buildDate}
     note: ''
-          Gitblit uses Servlet 3.0 and thus drops support for Tomcat 6.
+          Gitblit uses Servlet 3.0 and thus drops support for Tomcat 6. Run on Tomcat 6 at your own risk. 
 
           With the update to Lucene 5.5.2 reindexing of the tickets is necessary. This is done automatically during the first server start after an upgrade. Depending on the amount of tickets you have, this could take a little while. The old index is kept, so that a downgrade is still possible without losing information. The old index can be deleted, when a downgrade is no longer required.
 

diff --git a/src/site/faq.mkd b/src/site/faq.mkd
index 160808d6f45253d6de079714425da5e7810ccffc..4b5d2d613e3ef8efd1866e957470762ebbc0df9e 100644 (file)
--- a/src/site/faq.mkd
+++ b/src/site/faq.mkd
@@ -2,7 +2,7 @@
 \r
 ### push failed for branch (n/a (unpacker error))\r
 \r
-This is a bug in JGit (issue-408).  TLDR: Newer git clients are optimized to send less data on the wire.  JGit expects complete data to be sent, but there are scenarios where native git can optimize-out sending objects.  By default, JGit requires everything sent be complete and referenceable.\r
+This is a bug in JGit (issue-704).  TLDR: Newer git clients are optimized to send less data on the wire.  JGit expects complete data to be sent, but there are scenarios where native git can optimize-out sending objects.  By default, JGit requires everything sent be complete and referenceable.\r
 \r
 If you experience this, the workaround is to temporarily disable the reachable check for the receive pack, push, and then re-enable the setting.\r
 \r