瀏覽代碼

Correct issue in FAQ page to link to GitHub issue.

tags/r1.9.0
Florian Zschocke 4 年之前
父節點
當前提交
894c825838
共有 2 個檔案被更改,包括 2 行新增2 行删除
  1. 1
    1
      releases.moxie
  2. 1
    1
      src/site/faq.mkd

+ 1
- 1
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.


+ 1
- 1
src/site/faq.mkd 查看文件

@@ -2,7 +2,7 @@
### push failed for branch (n/a (unpacker error))
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.
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.
If you experience this, the workaround is to temporarily disable the reachable check for the receive pack, push, and then re-enable the setting.

Loading…
取消
儲存