Brian Ploetz
banner
brianploetz.bsky.social
Brian Ploetz
@brianploetz.bsky.social
Software development, distributed systems, music, sports, tequila.
Smack it up, flip it, rub it down, oh nooooo........that list is POISON......
October 3, 2025 at 8:46 PM
Every. Single. Time.
September 10, 2025 at 6:06 PM
TikTok
June 30, 2025 at 8:56 PM
‪@willcalhoun.bsky.social‬ how do you even reach that cymbal?! 😂
June 25, 2025 at 3:01 PM
Fucking murder's row right there
June 11, 2025 at 4:28 PM
Congrats!!
April 29, 2025 at 3:07 PM
You're missing the point. I'm not comparing him to Brady. I'm saying it's all a giant crap shoot and NO ONE can predict how one will fare in the pros vs how they did in college.
April 3, 2025 at 4:18 PM
I know another Patriots QB that was also drafted in the 6th round that went on to be pretty good after an "inconsistent" college career. On the flip side, how many studs coming out of college completely flopped in the NFL? Too many to name. College performance does not predict pro performance.
April 3, 2025 at 4:13 PM
Huh? What do you mean?
April 3, 2025 at 2:32 PM
Dallas got a steal, Pats got screwed. This kid is going to be a really good starter sooner rather than later.
April 3, 2025 at 2:23 PM
you look great though
March 26, 2025 at 3:21 PM
said every programmer ever
March 14, 2025 at 6:42 PM
I see. In that case what I would do is push master up as a new release-9.4 branch, and then push up the 10 branch as the new master. Depending on how the 10 branch was born and whether or not it has been getting updates from master or not, you may need to force push it to become the new master.
March 4, 2025 at 7:59 PM
Bisect assumes a linear commit history, but you can pass an option to tell it which parent to follow should this situation arise (as I understand it). Not sure if that's more or less cumbersome than rebasing. It might help to lay out what your current branching strategy is?
March 4, 2025 at 7:48 PM
Yes, hence my follow up Q on why you want to avoid the merge commit in the first place
March 4, 2025 at 7:34 PM
(though I'm curious why you think the merge commit would be a bad thing)
March 4, 2025 at 7:32 PM
Rebase the JRuby 10 branch on top of master, and then merge it back to master, which should then be a fast forward without any merge commit. Then push and tag master as JRuby 10. You can do the rebase on a new branch off of 10 if you're worried about messing it up.
March 4, 2025 at 7:26 PM
🤯
February 24, 2025 at 5:47 PM
*slow clap*
February 13, 2025 at 3:18 PM
It's gonna be a pain in the ass to get a keg from Packard's to your apartment in a canoe for that rager Friday night.
December 11, 2024 at 6:49 PM
You're reminded of it every time their site is having issues and you see the Unicorn error page. :)
December 9, 2024 at 6:02 PM