Overview
| Artifact ID: | 82645e76b6f0306599c48d1dc46c652747e84aba |
|---|---|
| Ticket: | 45a1b87a23afc27c8c59aaca225ea55bb7187faa
fossil merge should trigger pull with autosync |
| User & Date: | viriketo 2011-06-21 07:05:08 |
Changes
- comment changed to:
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?
- foundin changed to: "[74cbfc69ad] 2011-06-21"
- status changed to: "Open"
- title changed to: "fossil merge should trigger pull with autosync"
- type changed to: "Code_Defect"