jj-evolog(1) General Commands Manual jj-evolog(1)

jj-evolog - Show how a change has evolved over time

jj evolog [-r|--revision] [-n|--limit] [--reversed] [--no-graph] [-T|--template] [-p|--patch] [-s|--summary] [--stat] [--types] [--name-only] [--git] [--color-words] [--tool] [--context] [--ignore-all-space] [--ignore-space-change] [-R|--repository] [--ignore-working-copy] [--ignore-immutable] [--at-operation] [--debug] [--color] [--quiet] [--no-pager] [--config] [--config-file] [-h|--help]

Show how a change has evolved over time

Lists the previous commits which a change has pointed to. The current commit of a change evolves when the change is updated, rebased, etc.

Limit number of revisions to show

Applied after revisions are reordered topologically, but before being reversed.

Show revisions in the opposite order (older revisions first)
Don't show the graph, show a flat list of revisions
Render each revision using the given template

Run `jj log -T` to list the built-in templates.

You can also specify arbitrary [template expressions] using the [built-in keywords].

[template expression]: https://jj-vcs.github.io/jj/latest/templates/

[built-in keywords]: https://jj-vcs.github.io/jj/latest/templates/#commit-keywords

Show patch compared to the previous version of this change

If the previous version has different parents, it will be temporarily rebased to the parents of the new version, so the diff is not contaminated by unrelated changes.

For each path, show only whether it was modified, added, or deleted
Show a histogram of the changes
For each path, show only its type before and after

The diff is shown as two letters. The first letter indicates the type before and the second letter indicates the type after. '-' indicates that the path was not present, 'F' represents a regular file, `L' represents a symlink, 'C' represents a conflict, and 'G' represents a Git submodule.

For each path, show only its path

Typically useful for shell commands like: `jj diff -r @- --name-only | xargs perl -pi -e's/OLD/NEW/g`

Show a Git-format diff
Show a word-level diff with changes indicated only by color
Generate diff by external command
Number of lines of context to show
Ignore whitespace when comparing lines
Ignore changes in amount of whitespace when comparing lines
Path to repository to operate on

By default, Jujutsu searches for the closest .jj/ directory in an ancestor of the current working directory.

Don't snapshot the working copy, and don't update it

By default, Jujutsu snapshots the working copy at the beginning of every command. The working copy is also updated at the end of the command, if the command modified the working-copy commit (`@`). If you want to avoid snapshotting the working copy and instead see a possibly stale working-copy commit, you can use `--ignore-working-copy`. This may be useful e.g. in a command prompt, especially if you have another process that commits the working copy.

Loading the repository at a specific operation with `--at-operation` implies `--ignore-working-copy`.

Allow rewriting immutable commits

By default, Jujutsu prevents rewriting commits in the configured set of immutable commits. This option disables that check and lets you rewrite any commit but the root commit.

This option only affects the check. It does not affect the `immutable_heads()` revset or the `immutable` template keyword.

Operation to load the repo at

Operation to load the repo at. By default, Jujutsu loads the repo at the most recent operation, or at the merge of the divergent operations if any.

You can use `--at-op=<operation ID>` to see what the repo looked like at an earlier operation. For example `jj --at-op=<operation ID> st` will show you what `jj st` would have shown you when the given operation had just finished. `--at-op=@` is pretty much the same as the default except that divergent operations will never be merged.

Use `jj op log` to find the operation ID you want. Any unambiguous prefix of the operation ID is enough.

When loading the repo at an earlier operation, the working copy will be ignored, as if `--ignore-working-copy` had been specified.

It is possible to run mutating commands when loading the repo at an earlier operation. Doing that is equivalent to having run concurrent commands starting at the earlier operation. There's rarely a reason to do that, but it is possible.

Enable debug logging
When to colorize output

[possible values: always, never, debug, auto]

Silence non-primary command output

For example, `jj file list` will still list files, but it won't tell you if the working copy was snapshotted or if descendants were rebased.

Warnings and errors will still be printed.

Disable the pager
Additional configuration options (can be repeated)

The name should be specified as TOML dotted keys. The value should be specified as a TOML expression. If string value doesn't contain any TOML constructs (such as array notation), quotes can be omitted.

Additional configuration files (can be repeated)
Print help (see a summary with '-h')
evolog