Hi, On Tue, 2007-03-27 at 16:19 -0500, Allen Bierbaum wrote: > Gerrit Voss wrote: > > Hi, > > > > looking at the code actually I wonder why the image ever worked. > > Changed just unconditionally sets internal variables and this should > > loop forever all the time. > > > > > That is what we thought too, but then we thought "no way, everyone would > see this bug". :) > > > So the bug actually is that there are cases where it does not ;-) which > > after looking into some other code pieces becomes clear. > > > > I'll fix that one and try to work backward from there. > > > Good.
ok, I changed it and broke the image changed circle. Could you give it a try. > > Currently commit is setup to loop until all (including dependent) > > changes are committed. Which means if you create change circles it will > > loop forever. > > > > The options you have to limit the amount of loops are either to use > > a fixed upper limited on the number of loops or restrict the looping > > that per commit a container is only touched once. > > > > Both look artificial to me so I would prefer to have a loop free changed > > setup. > > > Any idea of a way to automatically detect when a loop happens in debug > mode and warn the user? Locally like for image in should be possible. Globally if you hop over n containers before coming back, I'm not quite sure. Let me think about it. gerrit ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
