kolan/Redmine
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merged r7658 from trunk

Browse Source 
scm: git: recovery and improve comments of fetching from 1.1
about harmful influence that git does not have the revision number.

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/branches/1.2-stable@7659 e93f8b46-1217-0410-a6f0-8f06a7374b81
This commit is contained in:
Toshi MARUYAMA 2011-10-27 00:41:37 +00:00
parent 83ab216d70
commit 8da22803be
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
app/models/repository/git.rb
View File

@ -92,6 +92,17 @@ class Repository::Git < Repository
options = {:report_last_commit => extra_report_last_commit}) options = {:report_last_commit => extra_report_last_commit})
end end
# With SCMs that have a sequential commit numbering,
# such as Subversion and Mercurial,
# Redmine is able to be clever and only fetch changesets
# going forward from the most recent one it knows about.
#
# However, Git does not have a sequential commit numbering.
#
# In order to fetch only new adding revisions,
# Redmine need to parse revisions per branch.
# Branch "last_scmid" is for this requirement.
#
# In Git and Mercurial, revisions are not in date order. # In Git and Mercurial, revisions are not in date order.
# Redmine Mercurial fixed issues. # Redmine Mercurial fixed issues.
# * Redmine Takes Too Long On Large Mercurial Repository # * Redmine Takes Too Long On Large Mercurial Repository