Furthermore i would ask if it would be useful, if any commit is dedicated to an issue, even if it wont complete it. Assume i would open issue '#123 A new feature is needed' and subsequently create 3 commits like '123 First commit', '123 Second commit' and '123 final commit'. Wouldn't this be more manageable?
Martin On 01/17/2012 12:27 PM, Martin Stein wrote: > I've noticed that there seems to be no convention for the note within a > commit message, about wich Github issue it addresses. > Often it looks like "This is an awesome commit. Fixes #X." as first > commit line, wich should be limited to 50 chars. Thus the phrase "Fixes > #X." wastes a lot of the documentation space. I know it's fussy, but > i'll wonder if something like "X This is an awesome commit." is fine? > > Greets, > Martin > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Genode-main mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/genode-main ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Genode-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/genode-main
