| Ticket UUID: | 45a1b87a23afc27c8c59aaca225ea55bb7187faa | ||
| Title: | fossil merge should trigger pull with autosync | ||
| Status: | Open | Type: | Code_Defect |
| Severity: | Priority: | ||
| Subsystem: | Resolution: | ||
| Last Modified: | 2011-06-21 07:05:08 | ||
| Version Found In: | [74cbfc69ad] 2011-06-21 | ||
| Description & Comments: | |||
|
I've had a problem running "fossil merge mainbranch", while in the upstream server (not in the local repository) there was a card that changed the "mainbranch" last checkin to a new branch, as you do with 'mistake'.
I use autosync on, and if "fossil merge mainbranch" had triggered a pull before merge, this problem would not have happened. Do you find it reasonable to trigger a pull on merge? | |||
View Ticket