"1 hour of my life I won't get back".
I wish. You know when this kind of bug happens to you it blows away half a day at least.
My Favourite Git Commit
281–290 of 389 posts
Re: My Favourite Git Commit
#282I'm always intrigued when developers complain that it was "[surprisingly short amount of time] of my life I won't get back." Maybe I'm not as clever, but I'm lucky if I fix an issue like that within a few hours. It can sometimes derail a workday. In fact, fixing in a few hours would be something worth celebrating!
Seriously. I'd count my lucky stars if I squished that one in under 4.
Re: My Favourite Git Commit
#283Earlier quoted context omitted.
This comment comes across really mean and judgmental. I didn’t read all of the original commit, but it read to me as informative and passionate with all of the frustrations solving a difficult problem comes with. Honestly, this comment is so over the top I can’t even detect whether you’re serious or not.
Opinions are relative. My over the topness is on purpose. The tone of the commit message resonates with exactly the same tone as my post (to me). The commit comment is filled with judgmental, caustic language toward the efforts of others. Yet my opinions about the persons view of “how to design language” are over the top. So you get my point entirely it seems. Are those people less passionate and deserving of such a…
> My over the topness is on purpose. The tone of the commit message resonates with exactly the same tone as my post (to me).
No, you see. The author of the commit was being humorous. You're just being an asshole.
> by a person who added a media player, a gold cup holder, on top of their foundations, walls, & plumbing?
C would be worthless if it wasn't for the programs that were built on it. To argue that the passion of the C developers is worth more than the passion of a media-player developer makes zero sense.
> A true craftsman would build a replacement without the perceived flaws.
Great thing the author never claimed to be "a true craftsman."
> I’ll give them props when they release their general purpose language
Ah, the "you can't criticize art unless you're an artist" argument.
Re: My Favourite Git Commit
#284Earlier quoted context omitted.
The pull request is a good place to put such a large amount of information. That would also be a good way to make sure it is seen by the broader team instead of burying it in commit history. You could make the argument that then it would not be part of the git history and therefore could be lost if you change hosts.
I will make that argument. The hosting is ephemeral, the commit message is eternal. Plus, what if you want to know what happened and you're simply offline? Let's not unnecessarily break the D in DVCS.
I never understood this philosophy. What makes Git more eternal than any other technology? Why is putting all of your data in one monolithic tool a good solution?
You might change your issue tracking solution. You might change your host solution. You might change your review platform. You might also change your VCS solution. Nothing is eternal.
Re: My Favourite Git Commit
#285Re: My Favourite Git Commit
#286OR you could just write Replace invalid ASCII char. Fixes rake error 'invalid byte sequence in US-ASCII'. I don't want your entire life story in my commit log.
> I don't want
Who cares.
Hope you enjoy this tone - your was the same.
Re: My Favourite Git Commit
#287Earlier quoted context omitted.
Then use `git log --oneline` and you don't have to see the lengthy details, until the inevitable day when you find you need them.
How do you surface them when you need them, though? git grep?
Git greps work if you're trying to search all the logs. I would think this detailed documentation would be most important when you're trying to understand a specific file or line of code. In that case, it's:
- git blame (who wrote this?)
- git show (look at the commit surfaced by blame)
Re: My Favourite Git Commit
#288Earlier quoted context omitted.
I will make that argument. The hosting is ephemeral, the commit message is eternal. Plus, what if you want to know what happened and you're simply offline? Let's not unnecessarily break the D in DVCS.
I never understood this philosophy. What makes Git more eternal than any other technology? Why is putting all of your data in one monolithic tool a good solution? You might change your issue tracking solution. You might change your host solution. You might change your review platform. You might also change your VCS solution. Nothing is eternal.
I didn't say anything about git. I said the commit messages are eternal, and none of those changes will change the commit messages (except, perhaps, changing the VCS, but usually that will preserve commit messages too).
Re: My Favourite Git Commit
#289OR you could just write Replace invalid ASCII char. Fixes rake error 'invalid byte sequence in US-ASCII'. I don't want your entire life story in my commit log.
> I don't want your entire life story in my commit log. I agree with this, but I think yours is too short. Scientific papers typically introduce enough information such that a person familiar with the field but not an expert in that particular area can understand generally what's going on. That's my ideal for a commit message as well: someone generally familiar with the codebase but who hasn't looked at this specific…
I really like that commit message - though it'd be nice to link to any sort of issue/task tracking ID that's relevant to that piece of work.
Re: My Favourite Git Commit
#290Earlier quoted context omitted.
That reminds me of the glorious https://en.wikipedia.org/wiki/File:JIS_and_Shift-JIS_variant... .
I have an Untagle game on my phone... is there an SVG editor that could do something similar?
I've found Graphviz / DOT to be surprisingly handy at times:
* https://www.graphviz.org/gallery/
* https://en.wikipedia.org/wiki/DOT_(graph_description_languag...