single developer on team using evolve
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Tue Apr 18 12:59:26 UTC 2023
On 4/18/23 13:27, Mitchell Elutovich wrote:
> 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?
the obsolescence marker are not going to get pushed to a repository that
does not have the feature enabled. So if you server does not have it
enabled, or the other developer client does not have it enabled, they
should not get the obsmarker.
What does your server setup and push/pull process looks like ? Do you
have the extension enabled server side ?
--
Pierre-Yves David
More information about the Evolve-testers
mailing list