You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the feedback from the users of our OpenGrok instance, the history browser part deserves lots of love. The main gripe is that it is not possible to comprehensively display last couple of commits to a repository and from there display all files changed by a commit and respective diffs.
Basically, the idea is to have something like presented by web interfaces for git or Mercurial. For example http://git.openssl.org/gitweb/?p=openssl.git;a=summary displays 3 sections: shortlog, tags and heads. Each of these sections has couple of links for its entries (like: commit details, commit diff, source tree view, download snapshot of the repo).
The problem of current way of dealing with history view for the whole repo is that it is not paginated. For big repos this can make the view completely unusable. This can be treated like a separate bug but the ultimate solution is to present dashboard like view as described above.
The text was updated successfully, but these errors were encountered:
Based on the feedback from the users of our OpenGrok instance, the history browser part deserves lots of love. The main gripe is that it is not possible to comprehensively display last couple of commits to a repository and from there display all files changed by a commit and respective diffs.
Basically, the idea is to have something like presented by web interfaces for git or Mercurial. For example http://git.openssl.org/gitweb/?p=openssl.git;a=summary displays 3 sections: shortlog, tags and heads. Each of these sections has couple of links for its entries (like: commit details, commit diff, source tree view, download snapshot of the repo).
The problem of current way of dealing with history view for the whole repo is that it is not paginated. For big repos this can make the view completely unusable. This can be treated like a separate bug but the ultimate solution is to present dashboard like view as described above.
The text was updated successfully, but these errors were encountered: