Matt

> figuring out exactly where to draw the API line will be a long and complex process +1 to that. It seems like a massive pain in the ass that...

> I would need at least two design docs before even starting this huge project. I agree, I implemented this to see if it was viable, try things out, see...

I've started work on the [design doc](https://docs.google.com/document/d/1rOKvutee5TVYpFhh_UDNZDxfUKyrJ8rjCNpFaNHOHwU/edit?resourcekey=0-922ApyoAjuXN_uTKqmCqjg&tab=t.0). For now, it just has a bunch of design questions we need answered before starting on the project, and my personal thoughts on...

I've created a prototype schema in #3869 (no functionality, just a schema). I've added Martin and Phillip as reviewers, as they seemed the most invested in it in the design...

Also, just double checked. The same problem also applies to `squash`, which is supposed to replace move.

Suppose you have a commit `A` with the file `f` containing: ``` foo bar baz ``` If we try to move the line `bar` to a *parent* commit `P` (the...

I happened to notice `jj unsquash` today. It seems to do what I specified, but in a more constrained form (no `--from` and `--to`), only supporting a revision and it's...

Yeah, I was aware it went the opposite way, I was mostly just voicing my thoughts on it. Move being ambiguous is a good point though. I still maintain that...

I've investigated further. Suppose we have a source commit `S` a parent commit `P`, and we select the diff `D` from `S - P`. Suppose in our example, `S =...

This feels somewhat related to #3575 and #3577. I think we could do it with minimal changes to the templating language. We'd just have to swap out the builtins for...