{"thread":{"id":"34152","subject":"git log: Add a switch to limit the number of displayed lines from the commit messages","startedAt":"2013-06-15T18:07:03Z","lastAt":"2013-06-17T06:18:52Z","messageCount":4,"participants":["Paul Menzel","Jonathan Nieder","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"220957","messageId":"1371319623.9845.34.camel@mattotaupa","threadId":"34152","inReplyTo":null,"subject":"git log: Add a switch to limit the number of displayed lines from the commit messages","fromName":"Paul Menzel","fromEmail":"paulepanter@users.sourceforge.net","sentAt":"2013-06-15T18:07:03Z","receivedAt":"2013-06-15T18:07:03Z","isPatch":false,"sender":{"key":"paulepanter@users.sourceforge.net","avatar":null},"body":"Dear git folks,\n\n\nthere are people out there disliking elaborate commit messages, as going\nover `git log` is tedious as you have to scroll a lot. As I do not like\nthe suggestion to make commit messages shorter by omitting certain\ndetails, a way to limit the number displayed lines of the commit\nmessages would be nice to have.\n\nThe switch `--format=oneline` exists already. Unfortunately a lot of\ncommits do not have a informative enough summary, so the first lines of\nthe commit message are still needed/desired to understand the commit\nmore.\n\nCould a switch be added, like `--commit-message-lines` (sorry for not\ncoming up with something better) to limit the number of displayed lines?\nThat would be great!\n\nFor older git versions, do you know of editor/pager options to achieve\nthis?\n\n\nThanks,\n\nPaul\n"},{"id":"220958","messageId":"20130615191905.GA3363@elie.Belkin","threadId":"34152","inReplyTo":"1371319623.9845.34.camel@mattotaupa","subject":"Re: git log: Add a switch to limit the number of displayed lines from the commit messages","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-06-15T19:19:05Z","receivedAt":"2013-06-15T19:19:05Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Paul,\n\nPaul Menzel wrote:\n\n> there are people out there disliking elaborate commit messages, as going\n> over `git log` is tedious as you have to scroll a lot. As I do not like\n> the suggestion to make commit messages shorter by omitting certain\n> details, a way to limit the number displayed lines of the commit\n> messages would be nice to have.\n\nHave you tried gitk or tig?  They split the screen so you can browse\nthrough commits, one per line, in one half and read the corresponding\ncommit messages and patches in the other.\n\nHope that helps,\nJonathan\n"},{"id":"221031","messageId":"7vd2rlic2q.fsf@alter.siamese.dyndns.org","threadId":"34152","inReplyTo":"20130615191905.GA3363@elie.Belkin","subject":"Re: git log: Add a switch to limit the number of displayed lines from the commit messages","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-06-17T04:41:01Z","receivedAt":"2013-06-17T04:41:01Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jonathan Nieder <jrnieder@gmail.com> writes:\n\n>> there are people out there disliking elaborate commit messages, as going\n>> over `git log` is tedious as you have to scroll a lot. As I do not like\n>> the suggestion to make commit messages shorter by omitting certain\n>> details, a way to limit the number displayed lines of the commit\n>> messages would be nice to have.\n>\n> Have you tried gitk or tig?  They split the screen so you can browse\n> through commits, one per line, in one half and read the corresponding\n> commit messages and patches in the other.\n\nOr inside \"less\" that is spawned by \"git log -p\", I often say this:\n\n    /^commit .*|^diff --git .*<ENTER>\n\nand navigate with 'n' and 'p'.\n"},{"id":"221036","messageId":"20130617061852.GA6942@elie.Belkin","threadId":"34152","inReplyTo":"7vd2rlic2q.fsf@alter.siamese.dyndns.org","subject":"Re: git log: Add a switch to limit the number of displayed lines from the commit messages","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-06-17T06:18:52Z","receivedAt":"2013-06-17T06:18:52Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Junio C Hamano wrote:\n\n> Or inside \"less\" that is spawned by \"git log -p\", I often say this:\n>\n>     /^commit .*|^diff --git .*<ENTER>\n>\n> and navigate with 'n' and 'p'.\n\nHm, that implies an interesting trick.  If I run\n\n\tLESS='FRSX +/^commit |^diff --git ' git log -p\n\nthen 'n' and shift+'n' can be used for navigating without having to\nspell out the /pattern to start by hand.\n"}]}