> git tags There are commands for manipulating tags (jj tag set, jj tag delete), and recently [1] support for fetching / pushing [1]: https://github.com/jj-vcs/jj/pull/9279
Rust is an example of "compiler magic" in this case. You're right about Zig, and reading the source [1] I'm still kind of impressed how unified they made comptime / runtime. [1]:…
I would call `jj absorb` a new feature (new if coming from git, I believe the idea was taken from hg). It moves diffs into the closest ancestor that touched those files/lines. Very useful for addressing reviews, then…
...no? On all counts. `jj ignore` is not a command. [1] There is no such thing as `.jjignore` files [2], [3]. `--no-snapshot` is not a flag, neither on `jj edit` nor in general. Additionally, it doesn't make sense…
I find it encourages linear history more by making rebasing easier. Definitely possible, the jj project itself uses a linear history.
The blockers for many are: - No support for LFS - No support for hooks (precommit, etc) - No? Bad? support for submodules - No? Bad? support for line ending styles If you don't care about those, you _should_ be able to…
> > if I'm understanding it right, turns r --[edit3]--> q --[edit2]--> p into r --[edit3]--> p. > You are right with the outcome but wrong about why. `jj abandon -r q` would turn `r --> q --> p` into `r --> p` Well, it…
You may be interested in the semi-standard `jj tug` alias [1], that moves "the most recent" bookmark up to `@-` [1]: https://github.com/jj-vcs/jj/discussions/5568
> git tags There are commands for manipulating tags (jj tag set, jj tag delete), and recently [1] support for fetching / pushing [1]: https://github.com/jj-vcs/jj/pull/9279
Rust is an example of "compiler magic" in this case. You're right about Zig, and reading the source [1] I'm still kind of impressed how unified they made comptime / runtime. [1]:…
I would call `jj absorb` a new feature (new if coming from git, I believe the idea was taken from hg). It moves diffs into the closest ancestor that touched those files/lines. Very useful for addressing reviews, then…
...no? On all counts. `jj ignore` is not a command. [1] There is no such thing as `.jjignore` files [2], [3]. `--no-snapshot` is not a flag, neither on `jj edit` nor in general. Additionally, it doesn't make sense…
I find it encourages linear history more by making rebasing easier. Definitely possible, the jj project itself uses a linear history.
The blockers for many are: - No support for LFS - No support for hooks (precommit, etc) - No? Bad? support for submodules - No? Bad? support for line ending styles If you don't care about those, you _should_ be able to…
> > if I'm understanding it right, turns r --[edit3]--> q --[edit2]--> p into r --[edit3]--> p. > You are right with the outcome but wrong about why. `jj abandon -r q` would turn `r --> q --> p` into `r --> p` Well, it…
You may be interested in the semi-standard `jj tug` alias [1], that moves "the most recent" bookmark up to `@-` [1]: https://github.com/jj-vcs/jj/discussions/5568