Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #3429
Closed
Open
Issue created Sep 23, 2019 by Alexey Nikolaev@aleksey-nikolaev

Optimize progress output with multiple git commands

The problem is that the output of the git.exe submodule is concatenated with the next git.exe submodule. If you can't remove the empty line after git.exe submodule - ok, but please add a new line before the next git.exe submodule

What steps will reproduce the problem?

The Submodule Update buttom

What is the expected output? What do you see instead?

I see:

git.exe submodule update --progress --init --recursive -- "3rdparty/gtest"

git.exe submodule update --progress --init --recursive -- "base"

Submodule path 'base': checked out '1ce9544fafca'
git.exe submodule update --progress --init --recursive -- "boot"

Submodule path 'boot': checked out 'f161e65f'
git.exe submodule update --progress --init --recursive -- "cv"

Submodule path 'cv': checked out '0e7e579aaf'
git.exe submodule update --progress --init --recursive -- "gui"


Success (47750 ms @ 23.09.2019 13:39:06)

I expect:

git.exe submodule update --progress --init --recursive -- "3rdparty/gtest"

git.exe submodule update --progress --init --recursive -- "base"
Submodule path 'base': checked out '1ce9fafca'

git.exe submodule update --progress --init --recursive -- "boot"
Submodule path 'boot': checked out 'f161ea465f'

git.exe submodule update --progress --init --recursive -- "cv"
Submodule path 'cv': checked out '0e7e57972af'

git.exe submodule update --progress --init --recursive -- "gui"


Success (47750 ms @ 23.09.2019 13:39:06)

What version of TortoiseGit and Git are you using? On what operating system?

  • TortoiseGit 2.8.0.0
  • git version 2.19.0.windows.1
Edited Sep 24, 2019 by Sven Strickroth
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking