@bnut@aus.social
@bnut@aus.social avatar

bnut

@bnut@aus.social

I enjoy making things that make it easier to make the things I enjoy. Mostly programming.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

alice_i_cecile, to bevy
@alice_i_cecile@mastodon.gamedev.place avatar

Starting in on the release notes for 0.14 today! So, so many small PRs: for both the tools and the individual content sections.

I have a half-dozen open right now; give me a review or two (low standard, these will get a real editing pass before publication) and help me start tomorrow's work with a fresh slate? 🥺

https://github.com/bevyengine/bevy-website/pulls/alice-i-cecile

bnut,
@bnut@aus.social avatar

@alice_i_cecile do you need someone with contributor/reviewer status to do the review?

They all look good to me, except 1198 has some TODOs in it (intentional?), and the rounded corners note is a bit non specific about what can be rounded, it’d be great to add a sentence for that.

b0rk, (edited ) to random
@b0rk@jvns.ca avatar

in git, what ways are there to "lose" a commit in a way that you CAN'T recover using the reflog (so that you need to iterate over every single commit in the repository if you want to find it?

The only ways I know (using git's normal tools) are:

  • using git stash drop or git stash pop to drop a stashed commit
  • waiting 90+ days to try to recover the commit (so that it expires from the reflog)
  • explicitly deleting the reflog in some way (rm -rf .git, git reflog expire, etc)
bnut,
@bnut@aus.social avatar

@b0rk if it was detached, or you have certain branch configs, then I think git gc can do it. I think similar commands can be configured to run automatically when your repo is large or slow.

bnut,
@bnut@aus.social avatar

@b0rk I think I’ve had detached commits lost due to the automatic cleanup because it was a large repo. Although it was a long time ago, and I don’t remember the exact diagnosis sorry.

bnut,
@bnut@aus.social avatar

@b0rk Yeah, I’m fairly sure it was git prune as part of automatic gc due to a large slow repo. This thing: “Auto packing the repository for optimum performance […]".

bnut,
@bnut@aus.social avatar

@b0rk It was a commit I cared about, which I detached through an explicit mistake (like reset), but I pruned it due to a much more unexpected implicit mistake. I believe it was pruned when fetching to see if the lost commit had been pushed.

decryption, to random

enjoying a talk about GlobalTalk from @DrJosh9000

image/jpeg

bnut,
@bnut@aus.social avatar

@decryption @DrJosh9000 this talk has a fun moire pattern

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • JUstTest
  • khanakhh
  • DreamBathrooms
  • InstantRegret
  • magazineikmin
  • tacticalgear
  • ethstaker
  • Youngstown
  • thenastyranch
  • slotface
  • rosin
  • kavyap
  • cisconetworking
  • mdbf
  • megavids
  • Durango
  • tester
  • Leos
  • GTA5RPClips
  • ngwrru68w68
  • everett
  • modclub
  • cubers
  • normalnudes
  • provamag3
  • osvaldo12
  • anitta
  • lostlight
  • All magazines
    •