Glen Choo
Glen Choo
Anecdotally, I've run into this fairly often by invoking `jj` commands interactively via `fzf` https://gist.github.com/chooglen/c76b2a6950aade154408fad2c42f97d7
This section: ``` Junio also suggested not distinguishing between '' and '' arguments in the `git help` documentation as when we will have enough man pages in different sections, we...
A band-aid might be to add args to `jj git export` to control which branches get exported. e.g. in this particular instance, I only care about the branch I was...
Applying the changes and diffing them will be much better, I think. Generalized interdiff sounds good, and as a first pass we could match commits based on change id. This...
> That might be true on the Git ML, but is it true elsewhere? I personally quite often rebase PRs (even though I know GitHub deals poorly with it). True....
Ah, yes I had a branch pointing to one of those commits. Maybe that wasn't the best example. Here's another one: ``` o E (branch-foo) | o D | o...
In another instance, `jj` thought that I had rewritten some commits in Git, but I actually didn't. I don't have a good handle of the reproduction recipe or what the...
> the Git branch pointing to C was removed (or moved) IIRC, that's the exact opposite of what happened. I created a jj branch at C, and (since my jj...
> We could create a new working-copy commit in each submodule when you check out a commit in the superproject. If we're thinking of the superproject and submodules as separate...