Repository: git / view all revision fails with branches
while investigating options for #4547 I came across the fact that the "View all revisions" functionality (RepositoriesController#revisions) blindly checks the changesets table and doesn't care about branches.
This leads to revisions of different branched being intermixed when using redmine with git repositories.
To fix this one, of the solutions provided in #4547 only always using git and never using the changesets table or adding branches/parents to the changesets table would work.
Personally, I'd be tempted to just shell out and keep the changesets table empty in case of git.
#2 Updated by Adam Soltys over 9 years ago
Oh I should mention -- I also considered abandoning redmine's changesets model in favour of just shelling out to git all the time, but doing so would prevent us from linking commits to issues by referencing issue numbers in commit messages which is a pretty powerful feature of redmine that I didn't want to lose.
Same goes for the repository "entries" model which comes into play when browsing the repository tree. I wish we could just shell out to git for that too instead of having to record all the file/filetype/size info in the database, but redmine's whole repository browser is built around this "SCM Agnostic" model and I didn't have the time to engineer around that fact.
#5 Updated by Toshi MARUYAMA over 8 years ago
- Status changed from New to Closed
From r2840 to r3394 in trunk and from 0.9.0 to 0.9.3(r3501) , Redmine reads all revisions in fetching.
But, after r3394 in trunk and after 0.9.3(r3501) , Redmine reads only one week revisions in fetching.
This is #7146 issue.
This issue affected version is 0.9.0 and it was fixed from 0.9.0 to 0.9.2.
So, I close this issue.