On 28 May 2013 18:30, Louis des Landes <louis obsidian com au> wrote:I don't know what the right choice is here, but it's going to be a
> Having a browse through at the moment.
>
> Some quick questions:
> * get_commit_message_prefill - you use a file (.git/MERGE_MSG) which only
> exists when git has just done a merge? Bazaar doesn't have an equivalent
> here, although I guess we could check if there's a pending merge and put
> some text in manually, but I feel this is the wrong choice.
VC-by-VC thing. This was added so that *if* there is a pre-filled
commit message, then we pick it up. In other words, if, when you went
to git commit from the command line, there would have already been a
commit message waiting for you to edit, then we try to use that. For
reference, this was added to fix
https://bugzilla.gnome.org/show_bug.cgi?id=699400.
> * Should the various commit/diff/update/add/remove/revert methods use theYeah, there's duplication because until a couple of weekends ago we
> existing <method>_command (diff_command etc) methods? There seems to be some
> duplication here, but I'm guessing it's a WIP.
needed the blah_command functions for sensitivity setting. Any
duplicates of those can now be removed as long as the module
implements update_actions_for_paths().