Fossil

View Ticket
Login

View Ticket

Plaintext
2024-01-29
09:23 • Closed ticket [e0f68fcf21]: Merge directive (i.e. patch with history) plus 2 other changes ... (artifact: 4c4f36ef53 user: stephan)
2011-01-26
13:25 • Ticket [e0f68fcf21]: 2 changes ... (artifact: e324406cd9 user: anonymous)
11:35 • Ticket [e0f68fcf21]: 2 changes ... (artifact: 00dca30e34 user: dmitry)
04:27 • New ticket [e0f68fcf21]. ... (artifact: 249076f14d user: anonymous)
Ticket Hash: e0f68fcf2195aa080eaee150d668b88b98ccded7
Title: Merge directive (i.e. patch with history)
Status: Closed Type: Feature_Request
Severity: Minor Priority:
Subsystem: Resolution: Overcome_By_Events
Last Modified: 2024-01-29 09:23:36
Version Found In:
Description:
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:

  1. Clone original repository.
  2. Make your changes.
  3. 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').

User Comments:
added on 2024-01-29 09:23:36: 
Closing as part of periodic cleanup.