bengesoff

4 ms·

1.
by bengesoff 6mo ago
Thanks for the feedback! The reason I like having the duplicate change as the working copy and squashing it down into the review change is that with colocated Git mode, my IDE highlights all the working copy changes as if they were uncommit
2.
by bengesoff 6mo ago
This is very nice, I just tried it, thanks for the suggestion. I was messing around with rebasing subsequent PR updates onto the review commit but it got a bit messy with conflicts. The `jj restore` should solve it
3.
by bengesoff 6mo ago
I’ve been using it too, definitely recommend!
4.
Reviewing Large Changes with Jujutsu(ben.gesoff.uk)
108 points by bengesoff 6mo ago|16 comments
5.
Reviewing Large Changes with Jujutsu(bengesoff.leaflet.pub)
1 points by bengesoff 7mo ago|0 comments
6.
by bengesoff 1y ago
FYI if you click the share icon on a Kagi search, then others can see the results without needing to have a Kagi subscription themselves, e.g. https://kagi.com/search?q=copywork&r=ae&sh=d9jIEVVKaHzifbixh... ( https:
7.
by bengesoff 10y ago
Maybe the refrigerator is the dock!
8.
by bengesoff 10y ago
On behalf of my friend: https://autono.ml It is a wrapper over DuckDuckGo which redirects all searches without bangs to Google. It also changes the bang operator (!) to the open square bracket ([) because it is easier to type. V
9.
by bengesoff 10y ago
Good point sir
10.
by bengesoff 10y ago
I haven't simulated this to check but it may be the case that IO pins become a limiting factor. The Cyclone IV has 153 IO pins so the design would have to use less than ~15 to be able to fit 10 copies on.
11.
Sharp Shows Off IZGO Free Form Display(thenextweb.com)
1 points by bengesoff 12y ago|0 comments