Repository metrics
- Stars
- Â (28,830 stars)
- PR merge metrics
-  (å¹³åããŒãž 23d 5h) (30d ã§ 46 merged PRs)
説æ
Consider a jj repo with the following jj log -p output:
@ wutluqlk (no email set) 2025-10-22 20:26:42 f70513d9
â (empty) (no description set)
â lwurnozr (no email set) 2025-10-22 20:26:42 git_head() 5cb58091
â Added bar.txt
â Added regular file bar.txt:
â (empty)
â lxnszsvq (no email set) 2025-10-22 20:26:42 50288a6f
â Added foo.txt
â Added regular file foo.txt:
â (empty)
â zzzzzzzz root() 00000000
Now I am just interested in the foo.txt file for the moment, so I limit the checked out files using jj sparse set --clear --add foo.txt. While this works as intended the jj log output still mentions the revision lwurnozr shown above, which is solely about files (well, in this example it's just bar.txt) I am currently not interested in.
For use cases like this I'd like to have a fileset function sparse(), which evaluates to a file set contained in the current sparse checkout. With such a function at hand I could use jj log -p -r 'files(sparse()) | empty()' to obtain a (potentially much) shorter output that contains indeed only the relevant changes:
@ wutluqlk (no email set) 2025-10-22 20:26:42 f70513d9
â (empty) (no description set)
~ (elided revisions)
â lxnszsvq (no email set) 2025-10-22 20:26:42 50288a6f
â Added foo.txt
â Added regular file foo.txt:
â (empty)
â zzzzzzzz root() 00000000