tag:blogger.com,1999:blog-6112936277054198647.post8977054387341837146..comments2024-03-12T00:42:06.642+10:00Comments on Who-T: On commit messagesPeter Huttererhttp://www.blogger.com/profile/17204066043271384535noreply@blogger.comBlogger15125tag:blogger.com,1999:blog-6112936277054198647.post-49929126649958964222017-06-29T03:34:59.723+10:002017-06-29T03:34:59.723+10:00Appreciated thisAppreciated thisNg Kah Faihttps://www.blogger.com/profile/01790017770315912180noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-83677539635512423592017-06-14T17:59:53.345+10:002017-06-14T17:59:53.345+10:00Hi,
one thing that kills me is uses of abbrevatio...Hi,<br /><br />one thing that kills me is uses of <b>abbrevations</b>.<br />By all means decipher _all_ of them at least _once_ in your text.<br />When you are new to Agile (or whatever),<br />than those are hard to decipher,<br />and sometimes search in google can mislead you.<br /> Going to the point: what is <b>SCM</b> ?<br />First guess (from google) is <b>Software Configuration Management</b>.<br />Is this correct ?Anonymoushttps://www.blogger.com/profile/13739039796368673258noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-20920650451590629962015-08-05T03:51:36.898+10:002015-08-05T03:51:36.898+10:00Unfortunately, whereas a change may occur over sev...Unfortunately, whereas a change may occur over several files, as well as documentation, this...<br /><br /> git add -u<br /><br />...which is the syntax for uploading those things with changes, puts the *same* commit message on everything on Github, instead of providing a means to supply the appropriate material(s.)<br /><br />The end result is that the top line, which is all one sees on Github without a click, is generally *not* a meaningful line for at least one of the changed files where there is more than one.<br /><br />So it's not always about the procedure of the author. Sometimes the tools are flawed.<br /><br />As a friend mentioned, it'd be much better if, on Github, they simply put "last changed on X date" in there, rather than a header line that is, in many cases, destined to be irrelevant.<br /><br />I like to make a list of changes to all things and put it in there. But it doesn't show without a click, so the whole overview-thing... not very functional.fyngyrzhttps://www.blogger.com/profile/10609909498498355812noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-26565236357484493962015-06-18T08:16:17.172+10:002015-06-18T08:16:17.172+10:00Re "SCM is not a backup system"... it ca...Re "SCM is not a backup system"... it can be, but keep that crap on your own personal branch and only push the final polished version.Anonymoushttps://www.blogger.com/profile/08161727555143925995noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-61672283274095692842012-01-10T22:59:49.166+10:002012-01-10T22:59:49.166+10:00@Stefan: not just gitk. -w can be used whereever a...@Stefan: not just gitk. -w can be used whereever a diff is generated. `git log -p -w -M -M` is one of the real tools one should know.j.enghttps://www.blogger.com/profile/09615346206411435754noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-54198661165827188792010-07-07T22:44:21.069+10:002010-07-07T22:44:21.069+10:00@Stefan, if you put 100 lines code under if () {} ...@Stefan, if you put 100 lines code under if () {} block you are most likely doing wrong thing.0andriyhttps://www.blogger.com/profile/14465968666368229947noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-6538512407122596982009-12-31T18:27:26.201+10:002009-12-31T18:27:26.201+10:00Thanks, very good post. I've recommended this ...Thanks, very good post. I've recommended this to a few people already - and I'm sure there will be more still - and mentioned it in my post about Subversion (and why no one should be using it anymore.)Oliver McFaddenhttps://www.blogger.com/profile/06947239359915728130noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-88202575683474193992009-12-31T03:15:53.535+10:002009-12-31T03:15:53.535+10:00When somebody says "but I'm the only one ...When somebody says "but I'm the only one working on it" gently remind him that three months down the road he won't remember the details of <i>why</i> he made such a change as he does right now, without a usable commit log message.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-34228458599488449892009-12-29T12:25:56.599+10:002009-12-29T12:25:56.599+10:00Very helpful. Thanks so much for formulating these...Very helpful. Thanks so much for formulating these suggestions. Agree about separating white space changes into separate, smaller commits. They're a logical unit of change, too.Wm Bentleyhttps://www.blogger.com/profile/08368757719301228993noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-16547887862694107972009-12-29T03:27:46.682+10:002009-12-29T03:27:46.682+10:00Great post, except the thing about whitespace chan...Great post, except the thing about whitespace changes. I see way too many code drops. "Practices of an Agile Developer" says: "13. Keep you project releasable at all times" and "17. Develop in increments."Mike Sherovhttps://www.blogger.com/profile/14450704659162297741noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-5451320143818531142009-12-29T02:47:40.287+10:002009-12-29T02:47:40.287+10:00Good stuff, I've seen commit messages like &qu...Good stuff, I've seen commit messages like "Added Stuff" from really over worked engineers. lolGreghttps://www.blogger.com/profile/14532699252481128738noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-79850568999138465872009-12-29T01:50:44.804+10:002009-12-29T01:50:44.804+10:00Very nice post. I will make myself to comment the ...Very nice post. I will make myself to comment the message of each functionality from now.<br /><br />Thank You,<br />Uma.uma mahesh varmahttps://www.blogger.com/profile/01952049893235262267noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-51645468158091297052009-12-29T00:32:25.121+10:002009-12-29T00:32:25.121+10:00Hi,
This is really great post. I need to save it ...Hi,<br /><br />This is really great post. I need to save it somewhere for my future collaborators ;)<br /><br />Regards,<br />MichalUnknownhttps://www.blogger.com/profile/01396195013429750393noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-15230178431741370192009-12-28T20:35:18.775+10:002009-12-28T20:35:18.775+10:00Thanks! This is really useful both to me and as a ...Thanks! This is really useful both to me and as a guide to be shown to other developers. Good reasoning too :)spbnickhttps://www.blogger.com/profile/09200421829965970954noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-13683309298888984472009-12-28T19:36:11.474+10:002009-12-28T19:36:11.474+10:00Good patch viewers (gitk) have an option to hide w...Good patch viewers (gitk) have an option to hide whitespace changes :)<br />This helps in cases where the reindentation was an important part of the patch, too (like putting 100 lines of code in a if () {...} block).Unknownhttps://www.blogger.com/profile/10224704039679662467noreply@blogger.com