On Tue, Jan 06, 2015 at 02:33:27PM +0100, Konrad Zapalowicz wrote: > On 01/06, Sudip Mukherjee wrote: > > yes, i read the SubmittingPatches again. summary is the subject line. But > > then as Piotr Kubus has written that he could not find this rule in the > > documentaion, I also tried to find that in SubmittingPatches file and also > > in the Posting file of the development-process folder, but could not find > > it. Is it mentioned in some other file we missed ? > > Then it is an 'unwritten rule' :) You can observe it just be browsing > the git log commit messages - pick a few random and you will see. i don't need to veify it, I don't doubt the rule. if you see all the patches i have sent, i have always maintained a rule of 70. just curious why this 72 .. this one gives a reason why -
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html sudip > > Moreover in the http://git-scm.com/book/ch5-2.html the 72-character > columns are the example of the good commit message plus Linus says so: > > "we use 72-character columns for word-wrapping, except for quoted > material that has a specific line format." > > in one of his comments > https://github.com/torvalds/linux/pull/17#issuecomment-5661185 > > cheers, > konrad > > > sudip > > > > > > -- > > > -=( Ian Abbott @ MEV Ltd. E-mail: <abbo...@mev.co.uk> )=- > > > -=( Web: http://www.mev.co.uk/ )=- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
