[juped]

I love the amazing, advanced submission and review workflow you can see if you click anything with PATCH in it at https://public-inbox.org/git/. The best part is that it's fully integrated with Git!

It's distressing to me that Github spends so much money making Git worse. (There's some good parts of their whole product lineup, but the Git integration is supposed to be the centerpiece.)

[atq2119]

I agree that this is how development should work. But let's be fair: The claim that this "is fully integrated with Git" is at least misleading.

Yes, there's git format-patch, git send-email, and git am.

But what I would really like to see in that link you shared is links that go directly to commit hashes that I can git fetch locally to see a patch or patch set in context; and links between different versions of a patch set; and so on. After all, git am does sometimes fail, e.g. because you have an incompatible base revision. And being able to push with confidence the version that you had in the email is also a plus.

[juped]

Patches aren't to specific revisions, that's the Github straitjacket talking. They're patches.

They often are to specific blobs; those are recorded. So if they don't apply, use am -3.

Specific revisions are Junio Hamano's job, not a patch submitter's.

[Noumenon72]

All I see is normal code review comments plus diffs, but as an email thread instead of a UI that lets comments be attached to the code they're discussing. And it's hard to read because no markdown.