On Tue, Jul 12, 2011 at 11:29:57AM -0400, Andy Singleton wrote: > If you want to keep it as a mergeable branch (clearly relevant), > then maybe it's better just to add on as "svn newmerge" from the > beginning. If that approach is recommended, then maybe someone can > help by adding the stub for this command to "svn".
Adding such a stub will be the easiest of all tasks that lie before you and your team. So if you need a new subcommand, I would suggest to add the necessary stub code yourself, if only to get your feet wet with the Subversion code base. I don't mind new subcommands in principle, but I would oppose 'svn newmerge' as a name for a new subcommand. 'newmerge' is a good working title but not a good name for a subcommand. Overall, I'd prefer solutions which change 'svn merge' in a backwards-compatible manner.
