Issue 2022: obliterate stops at the last tag

Title	obliterate stops at the last tag
Priority	bug	Status	unknown
Milestone		Resolved in
Superseder		Nosy List	kowey
Assigned To		Topics	Performance, Regression, UI

Created on 2010-12-18.22:20:53 by kowey, last changed 2010-12-18.22:20:53 by kowey.

msg13384 (view)

Author: kowey

Date: 2010-12-18.22:20:50

OK, so this may be a regression against issue174 where it seems to have 
been thought of as being a bug.

It's also related to issue1241, but rollback seems to have a different 
behaviour from obliterate/unrecord so I'm making a separate ticket.

Note that we *tried* to remove this behaviour in patch458, but we 
restored the restriction when we discovered that it had unpleasant 
performance implications.  

So it looks like we either need to document this behaviour as a quirk, 
add a flag, or find a sane way to fix it

History
Date	User	Action	Args
2010-12-18 22:20:53	kowey	create
2010-12-18 22:21:03	kowey	link	patch458 issues

Issue 2022 obliterate stops at the last tag