Moving record into core

[Bill Barry]

+1

Please have some method that can take in a patch or changeset or 
something similar and outputs 2 of them (one for use, one for non-use) 
as well so that there is a way to programmatically call the 
functionality. THg and other guis could override this method and provide 
interfaces for it.

Dirkjan Ochtman wrote:
> I think it's high time.
>
> Game plan:
>
> - move hgext/record.py to mercurial/record.py
> - add -i/--interactive options to commit and qnew
> - add internal aliases for record and qrecord, to save the old-timers pain
>
> I'd like to take a more thorough look at the code after that and see
> if it can be cleaned up. Maybe we can split it up, some parts in
> patch.py, some parts in cmdutil? We should also look at doing revert
> -i, maybe qref -i, etc.
>
> Cheers,
>
> Dirkjan
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>
>