Fossil Forum
Post: Sharing patches within Fossil
Fossil of course has bundles and patches for sharing changes, but is there any better mechanism besides using textual patches or base64 encoding a binary patch into e.g. a forum post for sharing them, so that potential contributors only have to interact with Fossil?
(I was unable to find anything immediately obvious poking around the docs, so apologies in advance if this has an obvious answer.)
... is there any better mechanism besides using textual patches or base64 encoding a binary patch into e.g. a forum post for sharing them, so that potential contributors only have to interact with Fossil?
The only "all-fossil" approach which readily comes to mind is using a combination of the "patch" command and the /chat UI, and passing patches around that way. The chat CLI command could be used to attach patches, too. That requires, however, that your potential collaborators at least have /chat access.
Hypothetically...
Wiki pages support attachments - a capability inherited from Fossil's ancestor but not commonly used in fossil. It "would be possible" for those with wiki-edit access to attach patches to a wiki page, but then those would become part of the permanent record. /chat, on the other hand, is essentially transient - it can be configured to be long-lived, but it does not sync and individual messages can be deleted by either an admin or their own poster.
Also hypothetically...
If you trust that /uv won't be flooded with garbage, you "could" give upload-unversioned access to your contributors and they could drop off patches there. Those, like /chat messages, are transient.
If you trust that /uv won't be flooded with garbage [..] Those, like /chat messages, are transient.
Also unlike /chat, unversioned files can be synced through the wire protocol (even though it doesn't sync by default). Definitely can be useful, eg, I got all the official fossil binaries that way.