The branch, master has been updated
via 37f130fd89d02e77bf55cbd8da731d87bb4ab1e8 (commit)
via 4a45b0da5743f76f77c812d03ee625af10fb2a54 (commit)
from f696bb81f8499443eee9815e7adf8dbb6810506a (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log
The branch, v3-0-test has been updated
via a92280537071b5a9a9bc56fbeead14c6874d5a55 (commit)
from bdf46ea491801cdf8ff6f42c0a1ef51080cfc410 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-0-test
- Log -
The branch, master has been updated
via 808928c24ba409a3fad50cbadf1db5a9dac9ad91 (commit)
from 37f130fd89d02e77bf55cbd8da731d87bb4ab1e8 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
The branch, v3-4-test has been updated
via b20cace3a7c312f44f39390954bc087b888d9b27 (commit)
from a75c184cafbb80adb0a3b056e55608d2d263a0c6 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-4-test
- Log -
The branch, master has been updated
via da46c371006d7cb5bceba790070d805b303ade98 (commit)
from 808928c24ba409a3fad50cbadf1db5a9dac9ad91 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 842edcd2b08763a35dbdea3518fcc039aa70aad4 (commit)
from da46c371006d7cb5bceba790070d805b303ade98 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
Hi Tridge,
fixed a logic bug in the tevent nesting code
The event nesting code never triggered as nesting.level was never
greater than 1. The main event loop needs to increase the nesting
level by 1.
That was desired, why do you want to be called if
The branch, master has been updated
via 1524abd8bf12d82e1fb0063585fc9a465fc7bf9c (commit)
via 2c186be0df33664eea980c17720be41f25f91288 (commit)
from 842edcd2b08763a35dbdea3518fcc039aa70aad4 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log
The branch, master has been updated
via 045151b767c62ac1343e86cb3886107226e73fda (commit)
from 1524abd8bf12d82e1fb0063585fc9a465fc7bf9c (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
The branch, v3-4-test has been updated
via 59811de7a80d5ecdf090c116087c7a03ae27 (commit)
via 42a692da477d7986767ad90a15087aa8a2ebcb40 (commit)
via 990917cbe3f8cd00e2d13dd67ee752fffae94401 (commit)
via 98dd60a0e85d37945deaa997d87f5cb173eaaea9 (commit)
from
The branch, v3-3-test has been updated
via 3517388b5d5439ffe3f9629aaf826fa1dfbb4ba7 (commit)
from f846e0fcdf62333b44a16e5a392930189b512f9b (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-3-test
- Log -
The branch, v3-2-test has been updated
via 5ce5a9bea994d7db3d352d0800333d0fd0b833df (commit)
from 6c13360e195189f7afc70c5fda6ef27f46145b0b (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test
- Log -
The branch, master has been updated
via 3a6133d70202ef80ead4203740c000be5e93b288 (commit)
via f2243e8197aa064adea3da2a4d1c08250668943f (commit)
via d2e348b191ada5492538b7bdae1bb7cd3f639aba (commit)
via 97190ae184dff6450b1390c854f7426e2ee3f980 (commit)
via
The branch, v3-3-test has been updated
via 9bf3e129605d51483fd5ce47c90642f7e82ac102 (commit)
via 3b0f612c52e992cd130f5176432722bada3c64e4 (commit)
via 76c858c6fcb8111e3fd87a2a8aa2606ab06bb90a (commit)
via 0f7757e94bfa35d22a7349d78578685c0dba22d7 (commit)
from
The branch, v3-2-test has been updated
via 66faa809847ad60b8027ae86068f8d62c0d181ed (commit)
from 5ce5a9bea994d7db3d352d0800333d0fd0b833df (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-2-test
- Log -
The branch, v3-4-test has been updated
via 0ec1350d3d9272a6070950ba1d460523f53a628d (commit)
via 8a6f09cededf4167aea5f08e573bab51afcc0074 (commit)
via e858d192e1d7d6ab45ec247fbb776f5825e7fca5 (commit)
via 1a591aadb66d589171d236fc2f8bf2eb6d9ce499 (commit)
via
Hi Metze,
tevent_loop_wait() calls tevent_loop_once() internally,
see the tevent_common_loop_once() function.
I missed that, though it only seems to be true for the main
backends. The liboop backend doesn't call tevent_common_loop_once.
We're tying ourselves in a pretty set of knots here
tri...@samba.org schrieb:
Hi Metze,
tevent_loop_wait() calls tevent_loop_once() internally,
see the tevent_common_loop_once() function.
I missed that, though it only seems to be true for the main
backends. The liboop backend doesn't call tevent_common_loop_once.
Backends which
The branch, master has been updated
via 1ef206524de589efeeef0544afbf7bfb37d99c15 (commit)
from 3a6133d70202ef80ead4203740c000be5e93b288 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 2de464a7658f91d2d01087080b984d52c3483426 (commit)
from 1ef206524de589efeeef0544afbf7bfb37d99c15 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
The branch, master has been updated
via 19de802c171f70ec4de102452afac52e2c0e548f (commit)
via d2de9b068c19a8eaac64f9cf4ea4aae153cffcd4 (commit)
via aa6dbcfc11b74c1e80728bc295d9612ba4eb1e64 (commit)
via 6713244d465b0cf69f1bba15744e05795ec2fda9 (commit)
via
The branch, v3-4-test has been updated
via 8630f2cbdfaaf8260615f16ba360b1281b666df5 (commit)
via 53965d391c08cc3b935f5bd86d2d95bb6fe89262 (commit)
via 48df86ca7f6d59b530597621862a619813a0568f (commit)
via ebf6d6d956a60c4f95baa4e148573bde933bdb2d (commit)
via
URL: http://build.samba.org/
--- /home/build/master/cache/broken_results.txt.old 2009-03-20
00:00:31.0 +
+++ /home/build/master/cache/broken_results.txt 2009-03-21 00:00:30.0
+
@@ -1,4 +1,4 @@
-Build status as of Fri Mar 20 00:00:02 2009
+Build status as of Sat Mar
The branch, master has been updated
via 960b75531530c05fcaaa7400e52f2b688a6e8d88 (commit)
via de1e3e2cf0c666a51b062ed5395906892beb53c0 (commit)
via 8f4e4d2e3039997106f9da3dcd5b057d99802ecf (commit)
via 4fff36f618420dea2e004f87ae5a2699eabd140a (commit)
via
The branch, master has been updated
via 62ab39dde37f5570b336b9db5b4e3c2e4640e877 (commit)
from 960b75531530c05fcaaa7400e52f2b688a6e8d88 (commit)
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit
25 matches
Mail list logo