How does jj log determine what revisions to show?

[rwjblue]

I'm trying to grok what is shown by jj log by default. How does it determine the list of revisions to show (vs what is elided)?

In a work repo, I have a ton of revisions shown for jj log that are completely unrelated to any commits or bookmarks that I have (e.g. jj bookmark list) but I'm not sure how to get rid of them from the default jj log display (or why they are there to begin with...).

In most repos I don't have this issue, I just see revisions that I've made (basically) and the path to trunk().

[joyously]

As it says in the Settings doc,

The default value for revsets.log is present(@) | ancestors(immutable_heads().., 2) | present(trunk()).

You can set it to a different revset. I don't think in revsets yet, so I think this default is a bit strange for a novice, but I don't know what to suggest as a better default.

[rwjblue]

That's great! I didn't notice that there was a default revset for it when I reviewed the jj help log output.

I guess now I need to dissect revset.log so I can figure out why all these extra entries exist .

[scott2000]

Basically, by default the log just shows anything that isn't immutable, as well as trunk() and @. It can also show an additional ancestor commit for context, even if that commit is immutable.

I think the default set of immutable commits is basically anything in trunk(), anything in an untracked remote bookmark, and anything in a tag. Everything else is considered mutable, so it'll show up in the log.

[rwjblue]

Gotcha, makes sense. I'm not sure why I'd have other commits than ones I've authored then. 🤔