[nh2]

Are you open to rename the "patches" terminology?

Apparently currently "1 patch = 1 pull request of e.g. multiple commits" in Radicle.

That confusing, since in Git a patch usually refers to a single commit:

    * git format-patch outputs 1 ".patch" file per commit.
    * Its output also enshrines that, in the subject lines that appear e.g. on Linux mailing lists: "[PATCH 1/2]", meaning "one of two patches in a patch series".

(That said, `git format-patch --stdout` can concatenate multiple commits into a single output, but it does not offer to write those into a single .patch file by itself.)

So when reading "Patches", I was intuitively unnecessarily scared that the tool cannot handle whole branches, and flattens out all commits.

Maybe "Patchsets"?

That's what kernel people apparently call them:

https://kernelnewbies.org/PatchPhilosophy#What_is_a_patchset...

https://kernelnewbies.org/PatchPhilosophy#Patches_are_git_co...

[endiangroup]

AD: Those are fair points, feel free to jump on our [zulip](https://radicle.zulipchat.com/#recent) and start a discussion there!

[nh2]

Unfortunately I won't have time for that; I just saw Radicle for the first time from this posting and wanted to drop-contribute what I think would reduce confusion for many people.

You'll have to take it from here :-)