Yuya Nishihara

> I think this could fit in well as a [revset](https://github.com/martinvonz/jj/blob/main/docs/revsets.md#functions) function; maybe `contents(foo)`, where `foo` is a string pattern? hg calls it `diffcontains(pattern)`. Implementing unoptimized version wouldn't be that...

> Do we have a concept of "pathsets" yet 🙂? No, not yet. Perhaps, a primary expression will be similar to string patterns (e.g. `glob:*.rs`), but the underlying implementation will...

Some idea on pattern naming. It's inconsistent in Mercurial. ### Axes * path normalization * cwd: cwd-relative filesystem path * root: workspace-relative path (or `RepoPath`) * unnormalized: raw string (such...

30984dae4a92fbee0dc0b0cbcbaefab2a93a2aa3

jj's internal view doesn't know about `/HEAD`, so we'll need to think that about first. It's a bit special because `/HEAD` is a symbolic ref whereas jj's refs (including local...

> jj doesn't explicitly handle symbolic refs, it just depends on all refs being resolved to a commit ID Correct. `jj` doesn't have a current/active branch (which is represented as...

> I do think it might be valuable to have a revset function for the remote's default branch. Perhaps, the revset syntax can be `HEAD@` just like `HEAD@git`. The underlying...

> * What do we do about the `jj init` command itself? > > * Leave it in, to only deal with the native backend. > The problem with this...

> `jj init --git-repo=.` says that `--git` and `--git-repo` are deprecated and suggests `jj git init` with no flags. I haven't updated this part. It's not wrong, but might be...

> Where the syntax `-r ` looks up and imports a commit, and possibly its ancestry, into `jj`'s view. `GITREF` should more or less be treated as Git would interpret...