BTW, when considering public facing repositories, Anton's suggestion is pretty neat. It prevents accidentally publish content. The default hg phases work well when pushing along a local development chain where you will want draft changes to be pushed along.
On Thu, Aug 10, 2023 at 8:13 AM Craig Ozancin <c.ozan...@gmail.com> wrote: > They can have similar results. What I explain is core mercurial phase > behavior. What Anton describes is a more fine grain control based on > revsets. In his example, only public changesets will push/pull unless > specifying a specific changeset using -r. > > On Thu, Aug 10, 2023 at 7:29 AM Friedrich Hagedorn <friedric...@gmx.de> > wrote: > >> Hello Craig, >> >> your explaination sounds good, but for me there is a contradiction with >> the advice from Anton: >> >> Am Thu, Aug 10, 2023 at 07:00:38AM -0600 schrieb Craig Ozancin: >> > Secret changeset are just like draft changeset with one difference. >> While >> > draft changesets can be shared between related repositories (hg push or >> hg >> > pull), secret changesets cannot be shared. >> >> vs. >> >> > > Am Wed, Aug 09, 2023 at 02:31:37PM -0300 schrieb Anton Shestakov: >> > > > If you're using secret phase to simply prevent accidentally pushing >> those >> > > > commits, maybe it'd be better to use a default revset instead. See >> `hg >> >> (I hope I didnt shorten the quotes too much...) >> >> Regards >> >> Friedrich >> >
_______________________________________________ Evolve-testers mailing list evolve-test...@lists.mercurial-scm.org https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
