On Mon, 20 Aug 2007, Dr. Peter Poeml wrote:
On Mon, Aug 20, 2007 at 10:25:39AM +0200, Dirk Stoecker wrote:
On Fri, 17 Aug 2007, Marcus Hüwe wrote:
during the usage of osc in last time I found 2 features missing:
a) When I'm e.g. in my home project I can't use osc ci -"mxxx" to checkin all the changes in the subprojects. Why?
A subproject and a project are 2 independent things. The subproject isn't related to "main" project and vice versa.
Ok. My error. I mean the packages. osc update and osc status and all the others work. Why not osc commit?
Maybe I don't understand what you mean, but this works for me:
poeml@batavia510 ~/bs/home:poeml % echo >> test/bar1 poeml@batavia510 ~/bs/home:poeml % echo >> test5/asdf poeml@batavia510 ~/bs/home:poeml % osc st test/bar1 test5/asdf M test/bar1 M test5/asdf poeml@batavia510 ~/bs/home:poeml % osc ci -m "fasel" test test5 Sending bar1 Transmitting file data . Committed revision 999. Sending asdf Transmitting file data . Committed revision 117.
Assuming only changes in test and test5 the following commands should be equal:
"osc status test test5" works "osc diff test test5" works "osc ci test test5" works
"osc status" works "osc diff" does not work "osc ci" does not work
"osc log" does not work (should show log for all packages) "osc log test test5" does not work "osc log" does not work
Comparing the behaviour to cvs and svn I would expect all of the above commands to work. Possibly with "osc ci" a security request can be added to ask if it is really meant to checkin everything :-)