The former no longer buys us anything.
Details
- Reviewers
durin42 pulkit - Group Reviewers
hg-reviewers - Commits
- rHG5c8230ca37f2: merge: replace calls to hg.updaterepo() by merge.update()
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
While I agree that resulting API is better than the previous one, however I think:
- This is an API breakage we can prevent
- merge.update() used to do a different thing before and now does something else before
Although, we don't provide any API's compatibility but preventing such breakages when we can sound a good thing to me. I think we can leave hg.updaterepo() as it is.
Want me to add a new merge.plain_update() or something like that instead?
Although, we don't provide any API's compatibility but preventing such breakages when we can sound a good thing to me. I think we can leave hg.updaterepo() as it is.
Sure, I can do that. So just leave it without callers you mean? Or drop this patch completely?
Let's leave hg.updaterepo() for now. If we want to remove, we can add a deprecation warning for few/one releases.
How about this question? Do you want me to call the new function merge.plain_update() instead? Another option is to do that while leaving merge.update() as a proxy to merge._update() with a call to ui.deprecwarn(). I'm fine with any of these 3 approaches (I'd prefer what I currently have -- it should be pretty simple for callers to check if _update() exists and prefer that for compatibility until they've finished a migration).
Although, we don't provide any API's compatibility but preventing such breakages when we can sound a good thing to me. I think we can leave hg.updaterepo() as it is.
Sure, I can do that. So just leave it without callers you mean? Or drop this patch completely?
Let's leave hg.updaterepo() for now. If we want to remove, we can add a deprecation warning for few/one releases.
Sure, will do. I'll assume you mean to leave it without callers (i.e. to not drop this entire patch).
I think a deprecation warning will be nice. However, I checked that (in all cases?) the old callers will end up with an error when trying to call a new function the old way, so we can document the replacement in the new merge.update() and that should be okay too I guess.
Although, we don't provide any API's compatibility but preventing such breakages when we can sound a good thing to me. I think we can leave hg.updaterepo() as it is.
Sure, I can do that. So just leave it without callers you mean? Or drop this patch completely?
Let's leave hg.updaterepo() for now. If we want to remove, we can add a deprecation warning for few/one releases.
Sure, will do. I'll assume you mean to leave it without callers (i.e. to not drop this entire patch).
Yes, function with no callers but some deprecation warning.