Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg-hgtk thg-hgtk
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 509
    • Issues 509
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • TortoiseHg
  • thg-hgtkthg-hgtk
  • Issues
  • #131

Closed
Open
Created Mar 26, 2009 by Bitbucket Importer@bitbucket_importerOwner

Log viewer change proposal

Created originally on Bitbucket by TON (Oleg Tazetdinov)

Currently the log viewer build a full list of changes for each changeset as soon as this changeset is selected. This results in very long processing time for changesets involving many files.

I have a changeset with updated regression results that contains about a hundred text files with multiple modifications. Some files are several Mb in size. It is not possible to wait till the log viewer fills in all the data.

The same problem occurs for the initial changests for legacy code when many files are added to the repository at once. It takes too long to wait for even the file list to be filled in if one wants to look for a single file.

I believe the usage model for so large changesets is to check the changes just in some selected files.

So my proposal is to fill the file list immediately and then generate the difference for each file separately as soon as it is selected in the file box.

Attachments: gmem_error1gmem_error2

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking