On 3/12/19 10:54 AM, Faheem Mitha wrote:
Yes, I realise that changing the phase of csets would suffice - that's
one of the side-effects of pushing to a publishing repos. I was
thinking that maybe I could just run an automated job to periodically
make all csets public for all csets that were at
On Tue, 12 Mar 2019, Aurélien Campéas wrote:
Hi Faheem,
Hi Aurélien,
I believe the point of topics is to emulate a "feature branch"
workflow familiar to git users (the equivalent of a publication
there would be to rebase over develop or master).
You need not "push to a publishing repo"
Hi Faheem,
I believe the point of topics is to emulate a "feature branch"
workflow familiar to git users (the equivalent of a publication
there would be to rebase over develop or master).
You need not "push to a publishing repo" to drop the topics
(this is a part of the tutorial I disagree
Hi folks,
I've been using Evolve for some time. One issue I've noticed is that
if I've doing a lot of amends over a period of time, to a file or
files, the rewriting mounts up quickly, because other commits get in
the way. The other day it occurred to me that a way around this would
be to do
