Nikolaus Rath <Nikolaus <at> rath.org> writes: > > On Sep 16 2015, Paul Moore <p.f.moore <at> gmail.com> wrote: > > On 16 September 2015 at 06:10, Stephen J. Turnbull <stephen <at> xemacs.org> wrote: > > In general you can do that by configuring the repository with > > [phases] > publish = False > > However, I believe BitBucket doesn't allow you to do that. But that's > not hg's fault.
Actually, BitBucket *does* support marking a repo as non-publishing. They don't yet support exchanging the bit of metadata that lets obsolete draft changes disappear, but I believe they have someone working on that now. (I don't work for them, so I'm potentially working off of outdated rumors.) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
