mq Deprecation plan

$/!\$ This is a DRAFT for discussion, and does not represent any firm decisions on future behavior.

1. mq features we don't yet have a replacement for

Maintaining a "floating" patch that can be applied and unapplied at whim. Use case is patches like "add debug logging." People want a well-known name they can reference. This could probably be done with unshelve that doesn't delete the bundle.
export/import/graft between repository workflow isn't as simple as cp

qapplied	log -r 'draft() and ::.'
qclone	not necessary
qdelete	histedit with 'drop'
qdiff	hg diff -r .^
qfinish	not necessary and/or 'hg phase --public'
qfold	histedit with 'fold'
qgoto	hg update
qguard	* no equivalent *
qheader	hg log -r . -T '{desc}\n'
qimport	hg import --partial
qnew	hg commit (does not handle empty commit)
qnext	hg log -r 'children(.)'
qpop	hg co .^
qprev	hg log -r .^
qpush	hg co -r 'children(.)'
qqueue	branches or bookmarks
qrefresh	hg amend (but we lack uncommit)
qrename	jungling with bookmark operation
qselect	* no equivalent *
qseries	hg log -r 'draft()'
qtop	hg id -B
qunapplied	hg log -r 'draft() - ::.'

-  ⇤ ← Revision 4 as of 2014-08-29 08:47:55 → 
  Size: 1780
  Editor: GregorySzorc
  Comment:
+   ← Revision 5 as of 2014-08-29 08:53:51 → ⇥
  Size: 1938
  Editor: GregorySzorc
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 17:
+Read comments at http://gregoryszorc.com/blog/2014/06/23/please-stop-using-mq/ and http://gregoryszorc.com/blog/2014/07/24/repository-centric-development/