>>>>> "Dean" == Dean Roehrich <Dean.Roehrich at sun.com> writes:
Dean> I've finally come around to experimenting with cdm in the Dean> mercurial repo for my project, and maybe I'm a bit handicapped by Dean> not having a history with wx. I'm told that (at least some of) the current subcommand names were chosen to match the wx subcommands. Whether your lack of wx experience is a handicap is debatable. ;-) Dean> Some of the command names exported by cdm are likely to collide Dean> with future mercurial commands. True, unfortunately. Dean> Cdm exports a long list of commands, and while 'hg help cdm' can Dean> be used to get just that list, wouldn't it be more in the spirit Dean> of mercurial if we put a prefix on our commands so they would all Dean> group together during 'hg -h'? This would have the added benefit Dean> of heading off any future name collisions. This sounds like something we should discuss with the Mercurial developers. (I can raise the issue unless someone else wants to.) A lot of the subcommands are specific to our development model, and so it's not clear that cdm (or even parts of cdm) will ever make it into Mercurial, even as a bundled extension. So I think there will always be some risk of name collision. I suppose we could prefix all the subcommands with "cdm", but that gets unwieldy fast. It might make more sense to give the subcommands less generic names. So, "pushlist" instead of "list", for example. Dean> I'm concerned about how we can track mercurial development when Dean> the day comes that there is a command name collision. If there's a name collision with Mercurial proper or a bundled extension, I think we'll almost certainly need to change our name. Which could be painful. mike
