Joy Reynolds

It might make more sense to reword some date references so that they are evergreen. In other words, refer to the year Git started, instead of how many years ago...

If the feature includes date calculations, you could test it my way also, and have a better result. > What’s your interest in Grace? My preference for version control (Breezy)...

It _is_ in `jj`'s README that the working copy is a commit and that is part of what unifies the interface. It seems rather odd to be suggesting changes to...

> we should not assume that people will read the README, or that they'll be using the CLI at all. I agree. What I was referring to is that having...

> I personally don't think anyone should try to use `jj edit` in the first day of using `jj`, and yet that's what _every single user we've asked_ at $dayjob...

> Is there any reason to _not_ show `(has changes)` when the commit is non-empty but has no description? I think it's more visual noise. Perhaps instead of "no description...

> this is kind of working as intended. I guess you can explain it away, but surely the intention is faulty since merge is a combining operation, not subtracting.

I was wondering a similar thing with Breezy (fork of Bazaar), which actually interops with Git with no trouble at all. I thought maybe both could use the import/expot functionality...

> He convinced me that we should not automatically propagate changes to copies and instead leave them conflicted. Then it becomes a simple yes/no question for the user whether to...

> **Case 2, good:** If I started my work before `X` happened and merged to `main` after `X` happened, I would presumably get a conflict when I rebase `A` onto...