necauqua

10 ms·

1.
by necauqua 2y ago
With what you described it sounds like jj is _literally_ exactly what you need, lol Give it a try, but also know that git branches and _topological_ branches are different things
2.
by necauqua 2y ago
There's an anti-footgun heuristic that asks "are you sure", basically, if the file about to be tracked is >=1mb, saved a lot of asses a lot of times. But also, if it is such a showstopper, you can disable auto-amend of _ne
3.
by necauqua 2y ago
It's hilarious that there are people who "don't get what problem jj is trying to solve". It seems like they just use git so little, barely for more that linearly committing, so they are not aware of it's shortcoming
4.
by necauqua 2y ago
I guess you don't use anything that's not preinstalled on your OS distribution then, lol Jesus, what a hater Maybe one day you'll become self-aware
5.
by necauqua 2y ago
I guess you could question the specific example, but to me the question sounded like "why would you do rebases". Like, for various reasons?. The point was that it's way easier and way safer to do rebases in jj, and it straigh
6.
by necauqua 2y ago
??.. wdym why, what?. Also this is just an example, there are a lot of very complex (from the point of git) things that are trivial like that in jj. Although if you're asking "why would we do that" then I don't even know
7.
by necauqua 2y ago
It's very obviously miles better because there's no global rebase state?. So you can just leave the conflict there an go work on something else then come back. Also it's not sequential like --continue you've mentioned. A
8.
by necauqua 2y ago
You can set `snapshot.auto-track` config to "none()" (which is a fileset, so you could actually have something like src/* there). That way, only files that were already present in the wc commit are amended, and new files are
9.
by necauqua 2y ago
While I understand your predicament, consider not giving up on jj just yet because of this. It is _exceedingly_ hard to lose files in jj, it's actually emotionally frustrating reading the line "most important thing [..] is to neve
10.
by necauqua 2y ago
In git terms (this is an analogy that is a bit wrong, but useful here), doing `jj new` after making some changes is the same as doing `git commit -am ""` then. Would you expect `git status` to "show you the changes, full st
11.
by necauqua 2y ago
It's `jj status`?.
12.
by necauqua 3y ago
Wow, you really just looked at a screenshot, got mad, and then went to write this shallow hate message. > my bane of "modern" CLI applications Ok boomer, I guess you're also a Rust hater too - because I love that every las