|
2024-01-31
| ||
| 05:13 | • Closed ticket [f5672eff7e]: a « patch » command plus 2 other changes ... (artifact: be962ea6a1 user: stephan) | |
|
2011-04-11
| ||
| 15:56 | • New ticket [f5672eff7e]. ... (artifact: 83bf992607 user: anonymous) | |
| Ticket Hash: | f5672eff7e99045d6b732f38141ecdf4d69699a5 | |||
| Title: | a « patch » command | |||
| Status: | Closed | Type: | Feature_Request | |
| Severity: | Minor | Priority: | ||
| Subsystem: | Resolution: | Overcome_By_Events | ||
| Last Modified: | 2024-01-31 05:13:02 | |||
| Version Found In: | 8caf7e1691 | |||
| Description: | ||||
|
A “fossil patch” command could be of some use for many users in my opinion.
The basic idea is: do whatever fossil merge --cherrypick does, but following multiple descendents at a time. The syntax would be:
Of course it would honor merge_cmd and other settings! | ||||
| User Comments: | ||||
added on 2024-01-31 05:13:02:
Closing as part of periodic cleanup. | ||||