moving non publishing changesets between secret and draft phases and back to secret
Mitchell Elutovich
melutovich at gmail.com
Thu Aug 10 14:44:59 UTC 2023
Craig: As there is no <alias>:pullrev, Anton's example was just to only
limit push to public changesets
Friedrich: Anthon was addressing some specific usage I had in how to
exchange changesets but not have them go to our public server. I believe
the usage of secret would be when one wants to indicate to oneself and
others that their changesets are not ready for others (or we need to
communicate first) or not planned for others.
For myself, I have a few secret changesets (some of this usage might not be
needed using some of Anthon's suggestions, but that requires everyone on
board)
- Today I created one in which I've got some staged work but I'm waiting
for someone else on our team to create for me my virtual server
certificates for it.
- I periodically have some experiments that used to be files hg did not
know about, however a hg purge instead of an hg prune removed them, now I'm
trying to get in the habit to commit them in a secret changeset to prevent
them from being accidentally removed.
On Thu, Aug 10, 2023 at 5:14 PM Craig Ozancin <c.ozancin at 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 <friedrich_h at 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-testers at lists.mercurial-scm.org
> https://lists.mercurial-scm.org/mailman/listinfo/mercurial-evolve-testers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20230810/da2afe43/attachment-0001.html>
More information about the Evolve-testers
mailing list