Yuya Nishihara

> I was suggesting changing the definition of "discardable" commits to include empty merge commits with no description. You are suggesting keeping the definition as-is, and merely having commands like...

> > I use jj abandon all the time start over. It's surprising to me if I can't use that because my current commit has multiple parents. > > Actually,...

> I would want to be able to do `jj new x y z; ; jj abandon` and still have x, y, and z as parents. Interesting. I've never considered...

> > In any case, I wouldn't want my empty merge commit get abandoned by `jj new somewhere_else`. > > If it has no description and no changes, is it...

> Right now, the two options I see are either what I suggested (making empty no-description commits discardable regardless of the number of parents) or to special-case `jj abandon` so...

Perhaps, the fraction part can be hidden by default. It's always zero in Git backend, and it wouldn't be important in op log either. FWIW, I prefer the current ISO...

> Are the timestamps not normalized at all? Does this affect sorting by date? Sorting isn't affected. The underlying data is `(utc_msec, tz_offset)` pair.

I prefer to see the raw metadata, but I don't mind if it's translated to local timezone. I don't like `.ago()`.

> `checkout_order([foo, bar, baz])` Perhaps, this can be achieved by some revset to resolve `@` in op log. #1283 suggests an infix op to resolve revset at a certain operation....

> If it simplifies things, I wouldn't mind if we added a specialized way of finding where @ pointed N steps back in the operation log. Implementation-wise, it'll be easier...