Waleed Khan

For reference, here is the Wiki page for the stack-related operation of `git-branchless prev/next`: https://github.com/arxanas/git-branchless/wiki/Command:-git-next,-git-prev#moving-to-the-top-or-bottom-of-the-stack. Switching to the bottom of a stack doesn't require understanding what a "stack" is (as...

>For example, I would want to move to the next commit that touched file foo, the next commit authored by me (or not me), or the next commit with a...

Although libgit2 doesn't support shallow clones, it seems like in this case, the error message is just of a missing parent commit? We'd have to handle that even if libgit2...

I guess https://github.com/martinvonz/jj/pull/2312 is a little imprecise: it's really meant to answer "how do I *interactively* commit certain changes", but the heading as written implies that it would answer how...

> Isn't 1 and 2 like literally the git author date and committer date? > Except "committer date" does not change on rebases which is actually sensible The first case...

I've mentioned this before: having some general `next`(/`prev`) function such that you can write `jj new 'next(conflict() & stack())'` would be pretty useful, where `next(x) = heads(@: & x:)`, or...

I think you mean roots(), not heads(). In fact, wouldn't latest(roots( conflict() & stack() )) work just as well? Here, there will usually only be one root, so latest will...

> The main reason hg and subsequently jj use positional args for paths is for shell expansion (like jj log *.txt) to work. We have to enclose revset expressions in...

@martinvonz Sorry, I didn't state/justify my assumptions. Git *will* expand `*.txt` on its own, separately from shell expansion, which means that you can write `git log -- '*.txt'` and have...

> I don't think the glob library supp Sentence cut off here? > I do think `jj log *.md docs/*.md` can be convenient. Would you require quoting both? Yes, in...