> On Oct 17, 2018, at 17:55, za3...@i2pmail.org wrote: > > Hi There, > > Im from I2P community and our developers using Monotone to develop the famous > anonymous protocol I2P (or the invisible internet project). > > Sadly monotone project died since 4 years ago, so we want to have > alternative. > > our conditions to make the development software to work well (specially with > I2P) , to have these criteria: > > - supports resume
You mean resumable clone operations? We don't have that today, but there's ongoing work to try and handle that. > - key signed checkins This is on our roadmap (https://www.mercurial-scm.org/wiki/CommitCustodyConcept and https://www.mercurial-scm.org/wiki/CommitSigningPlan) but nobody is (to my knowledge) tackling this work right now. > - revocation of keys/trust function implementation Same as previous. > - easy migration of mtn history into new system This as far as I know is easily done: `hg convert` ships with hg and should already support mtn. > does Mercurial support these options? if no, is it on the road map? if no, > then why not? Note that there'd probably be some fairly enthusiastic mentoring from existing committers on the commit signing bit, but that still means someone needs to volunteer to tackle what appears to be an at least somewhat challenging problem. > > Thank You! > > _______________________________________________ > Mercurial-devel mailing list > Mercurial-devel@mercurial-scm.org > https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
