Have "hg strip" blacklist stripped revisions?
Matt Mackall
mpm at selenic.com
Fri Nov 5 04:42:08 UTC 2010
On Thu, 2010-11-04 at 19:15 -0700, CG Linden wrote:
> An idea...
>
>
> After multiple occurrences of people committing back stripped
> revisions, I was wondering if it was possible to include a feature
> that would add changesets to a blacklist, and have pull/push fail if
> one of the blacklisted revs is to be included.
At the sprint, we discussed a plan for a related concept called 'liquid
hg' that would allow marking a set of changesets and their ancestors
'frozen' (permanent, can't be modified) and another set of changesets
and their descendants 'dead' (won't be propagated, may be
garbage-collected). This information would be propagated on push/pull
with the pushkeys mechanism we introduced in 1.5.
Changesets in between these two ranges would be 'liquid', meaning open
for modification with tools like MQ and rebase.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel
mailing list