Fossil SCM
Merge directive (i.e. patch with history)
e0f68fcf2195aa0…
· opened 15 years, 2 months ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Minor
- Resolution
- Overcome_By_Events
- Subsystem
- —
- Created
- Jan. 26, 2011 4:27 a.m.
Fossil makes it really easy to clone repos. It would be great if one could make "drive-by" contributions to an open source project by passing back fixes made in a cloned repos back to the developers without requesting write access for the repository.
Bazaar has a cool feature called "Merge directive" that packages all changes relative to the partent branch: http://doc.bazaar.canonical.com/bzr.2.2/en/user-guide/sending_changes.html
It would be cool if Fossil supported this feature as well
dmitry added on 2011-01-26 11:35:36 UTC: I think the DVCS way to do this is:
# Clone original repository. # Make your changes. # Send pull request, as in: "Hey, I've got this fixed, pull from https://url"
anonymous added on 2011-01-26 13:25:21 UTC: Right, that's the standard heavyweight way. Merge directive is a lightweight way of doing this. I think of is as series of commits represented as individual patches. The benefit over a single patch is that history is preserved. Maybe this feature isn't as important for Fossil. (I changed Severity of 'Minor').
Comments (1)
Closing as part of periodic cleanup.