Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 364
    • Issues 364
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #1252
Closed
Open
Created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

wrap commit logs per git conventions

By costin.l... on July 04, 2012 11:21 (imported from Google Code)


This is an improvement not a bug.

See http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

What is the expected output? What do you see instead?
When adding a message log it would be really handy to have tortoisegit do automatic line wrapping for the commit log as per git convention.

That is wrap the first line to 50 chars.

Wrap following lines to 72 chars. Ideally allow these limits to be configured.

What version of the product are you using? On what operating system?

Win 7 x64 Ultimate SP1 + 1.7.10.0

Please provide any additional information below.

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