single developer on team using evolve
Mitchell Elutovich
melutovich at gmail.com
Tue Apr 18 11:27:25 UTC 2023
My question is basically similar to this stackover question.
https://stackoverflow.com/questions/50763422/how-to-avoid-mercurial-obsolete-warning-on-clients-without-evolve-extension
I would like myself to start using the evolve extension, however I don't
think I can convince my entire team to use evolve, if they are going to get
messages like "obsolete feature not enabled but XY markers found!", I think
they will not be happy with me.
As in that question is there a way for "the server to not push the obsolete
data to clients without evolve enabled"? If not, would the following work
around help?
If I have an intermediate repo used to push to the shared server repo with
[phases]
publish = false
[extensions]
#evolve=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20230418/9ce3cf34/attachment-0001.html>
More information about the Evolve-testers
mailing list