Re: [Monotone-devel] kill_*_locally

[Thomas Keller]

Am 15.06.2010 14:33, schrieb Timothy Brownawell:
> There's a branch nvm.kill_certs_locally that adds a command
>    db kill_certs_locally SELECTOR CERTNAME [CERTVAL]
> and updates 'mtn cert' to accept a selector that can be multiple
> revisions instead of just one.
> 
> This also *removes* 'db kill_tag_locally' and
> 'db kill_branch_certs_locally'.

I'll have a look at it tonight.

> Does anyone think it's a really horrible idea to just remove those? I
> suppose it would also be possible to deprecate them by marking them
> hidden and making them print a warning to use kill_certs_locally instead.

Given that these commands should be used very rarely, that they aren't
available in automate and that the time between deprecation in 1.0 and
possible removal in 2.0 will be quite long, I vote for removing them for
1.0 already.

> If we are OK with just removing things, we could put this and
> kill_rev_locally as "mtn local kill_certs" and
> "mtn local kill_revision" instead of "mtn db kill_*_locally".

+1 (but hey, I proposed that :))

Thomas

-- 
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en

signature.asc
Description: OpenPGP digital signature