Christian Lohmaier wrote:
Hi *,
Hi,
Mercurial documentation as well as previous mails concerning this topic describe that you can create a cws in EIS, and that the outgoing repo is created when setting the state to new. http://wiki.services.openoffice.org/wiki/Mercurial/Cws#Creating_the_child_workspace_in_EIS reads: "As an alternative way you can use the EIS web fronted to create the CWS and set it to status 'new'. Don't forget to set the SCM property to 'HG'. " But that's not possible, as the only choices available are planned and finished.
Whoever wrote that paragraph didn't request a corresponding feature for EIS from tooling :-(
What you can do is to create a CWS in EIS setting it to "plannned" initially and some time later than use the "cws create" command on the commandline afterwards to really create it and set it´s state to new. This should work for currently used HG and previously used SVN SourceCode Control Mangement systems.
Setting a planned CWS to 'new' or initially setting to 'new' is currently probably only possible with some administrator rights in EIS.
If we would want to be able to directly set the CWS to 'new' in EIS for HG based ChildWorkspaces for everyone we could probably add such a feature, but it would eventually be some kind of tricky how to allow that than for HG based CWS and disallow that for other CWSs which are using other SCMs.
ciao Christian
ciao, Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tools.openoffice.org For additional commands, e-mail: dev-h...@tools.openoffice.org
