On Monday 24 January 2011 00:13:26 Eike Hein wrote: > > Yep - for the benefit of those who aren't used to the git > jargon (sorry for that), in git the convention is to for- > mat the commit message like this: > > <single line of about 50 chars, followed optionally by:> > <empty line> > <longer message> > > While deviating from this format is not particularly harm- > ful, git and various tools based on git 'rely' on this > convention to varying degrees. > Semi-OT: What is the empty line good for? Sometimes I just continue writing if the start of a long first sentence turns out to be a good summary.
- Re: Usefulness of Subject-header of git... Eike Hein
- Re: Usefulness of Subject-header of... Milian Wolff
- Re: Usefulness of Subject-head... Eike Hein
- Re: Usefulness of Subject-header of git commit mails Boudewijn Rempt
- Re: Usefulness of Subject-header of git commit ... Milian Wolff
- Re: Usefulness of Subject-header of git com... Eike Hein
- Re: Usefulness of Subject-header of git... Milian Wolff
- Re: Usefulness of Subject-header of... Boudewijn Rempt
- Re: Usefulness of Subject-header of git... Allan Sandfeld Jensen
- Re: Usefulness of Subject-header of... Eike Hein
- Re: Usefulness of Subject-head... Andreas Hartmetz
- Re: Usefulness of Subject-... Parker Coates
- Re: Usefulness of Subject-... Johannes Sixt
- Re: Usefulness of Subject-header of git com... Boudewijn Rempt
- Re: Usefulness of Subject-header of git commit mails Allan Sandfeld Jensen
- Re: Usefulness of Subject-header of git commit mails Tom Albers