Having more than three phases (was RFC: Phase UI (revset, phase command and others))

Laurens Holst laurens.nospam at grauw.nl
Thu Jan 5 07:36:55 CST 2012


Op 04-01-12 18:44, Augie Fackler schreef:
> On Tue, Jan 3, 2012 at 12:52 PM, Matt Mackall<mpm at selenic.com>  wrote:
>> ..except that every alternative I've seen proposed (obsoletion markers,
>> dead heads) is MORE ill-suited. We made the rules, we can break them
>> when appropriate. And I really don't see much wrong semantically with
>> saying "these draft/secret changesets are to henceforth be ignored for
>> log/push/pull and are subject to GC".
> I'm pretty sure we need to communicate trashed/obsoleted state as well
> - otherwise how can I publish RFC draft changesets for people to
> examine, and then have them get "deleted" later?

I would say that propagation should be taken care of by a mechanism on 
top of trashed changesets. I think a trash phase makes sense and is an 
improvement over what we have now (dumping bundles), and a good basis 
for further functionality that moves a changeset’s phase to trash under 
certain conditions.

Also personally I don’t much like the whole premise that others can 
“delete” my changesets just by pulling from them, so I can definitely 
see this propagation being optional / skippable.

~Laurens


More information about the Mercurial-devel mailing list