As somebody who reviews those first lines with some regularity (status reports, meetings, releases, etc.) if you could figure out an explanation that fit within 75-80 characters (as we asked in the SVN days), that would make my life a whole lot easier. It need not say everything, just provide a headline.
-Brad On Thu, 7 Aug 2014, Vassily Litvinov wrote: > Here are my considerations: > > * I often make the first line of my merge message quite long - this allows me > to summarize my changes more comfortably. > > * Within the message, it makes sense to me to have (a) one line per paragraph > and/or (b) restrict each line so it fits on one line when I view it using > 'git log' in my emacs (which implies <=75 chars). > > Although I can probably live with other arrangements as well. > > Vass > ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
