© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
great !
We'll think about rebase later (still an interesting idea to keep around)
About revert, I'm realizing that while resetting to origin/master is the wished behaviour for the two use-cases of the merges-in feature, it's really dangerous for other cases, since it would drop unpushed original changesets (so far the only use-case for revert is to redo a merge).
Maybe we could have that method react in different way if triggered via on-merge ? What do you think ?
In any case, we'll have to warn strongly in doc.