Ilya Grigoriev fa123bbfee docs: emphasize and clarify log revsets relevant to people coming from git ... I couldn't come up with a Git analogue of `jj log`, but I think it's OK leaving it as a TODO makes the point. Perhaps somebody can figure it out. Also, all the correspondences are not completely precise, so I didn't emphasize it every single time.		2024-01-31 15:51:40 -08:00
..
design
technical
branches.md	docs branches.md: insert definitions for related terms	2024-01-24 18:47:17 -08:00
cli-reference.md	docs: store output of jj util markdown-help, render it on the website	2024-01-30 14:58:32 -08:00
code-of-conduct.md
config.md	docs config.md Vim instructions: link to the Wiki instead of a gist	2023-12-17 22:16:02 -08:00
config.toml
conflicts.md
contributing.md	docs contributing.md: document using mold linker with nextest	2024-01-21 19:28:37 -08:00
FAQ.md	FAQ: Make a question clearer.	2024-01-29 20:42:26 +01:00
git-comparison.md	docs: emphasize and clarify log revsets relevant to people coming from git	2024-01-31 15:51:40 -08:00
git-compatibility.md
github.md
glossary.md	docs branches.md: insert definitions for related terms	2024-01-24 18:47:17 -08:00
index.md
install-and-setup.md
operation-log.md	op_walk: add support for op_id+ (children) operator	2024-01-02 10:30:08 +09:00
related-work.md
revsets.md	docs: emphasize and clarify log revsets relevant to people coming from git	2024-01-31 15:51:40 -08:00
sapling-comparison.md
templates.md	cli: give root operation special treatment in template (like root commit)	2024-01-14 10:15:14 -08:00
tutorial.md	docs: update CLI output in Tutorial	2024-01-08 19:59:59 +04:00
windows.md	docs: add notes for Windows users	2024-01-29 12:16:15 -08:00
working-copy.md