[fossil-users] 答复: fossil-users Digest, Vol 43, Issue 3
Hi, Ron: Thanks a lot! I think with or without open repository 'ops' in server, the server should act equally. This is the test: Content of tst_server.bat md D:\o cd /d D:\o if exist ops del /q ops if exist _FOSSIL_ del /q _FOSSIL_ fossil version @echo. @echo Please record the password and set it into tst_client.bat fossil new ops fossil server ops The result of run tst_server.bat is in tst_server.txt: D:\tst_server D:\md D:\o D:\cd /d D:\o D:\oif exist ops del /q ops D:\oif exist _FOSSIL_ del /q _FOSSIL_ D:\ofossil version This is fossil version 1.18 [df9da91ba8] 2011-07-13 23:03:41 UTC Please record the password and set it into tst_client.bat D:\ofossil new ops project-id: 23192a3021d29562f65a705ddc8dba8016070a32 server-id: ea446b3b950372ff8114dfb3e570cada9597beec admin-user: y00122496 (initial password is 3f57fe) D:\ofossil server ops Listening for HTTP requests on TCP port 8080 Type Ctrl-C to stop the HTTP server Then copy the password into tst_client.bat as follow: md D:\m cd /d D:\m if exist ops del /q ops if exist _FOSSIL_ del /q _FOSSIL_ fossil clone http://y00122496:3f57fe@y00122496:8080 ops fossil open ops dir client.txt fossil add client.txt fossil commit --comment Client1 fossil ls -l @echo. @echo Turn to server cd /d D:\o fossil open ops fossil ls -l @echo. @echo client.txt is NOT in the repository of server dir server.txt fossil add server.txt fossil commit --comment Server1 fossil ls -l @echo. @echo Turn to client cd /d D:\m fossil sync http://y00122496:3f57fe@y00122496:8080 fossil ls -l @echo. @echo server.txt is NOT in the repository of client The result of run tst_client.bat is in tst_client.txt: D:\q\fossil\tst_client D:\md D:\m D:\cd /d D:\m D:\mif exist ops del /q ops D:\mif exist _FOSSIL_ del /q _FOSSIL_ D:\mfossil clone http://y00122496:3f57fe@y00122496:8080 ops Bytes Cards Artifacts Deltas Sent: 53 1 0 0 Received: 344 5 1 0 Sent: 58 2 0 0 Received: 634 2 0 0 Total network traffic: 491 bytes sent, 1129 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 23192a3021d29562f65a705ddc8dba8016070a32 server-id: ff80810a3b3b768c1dec8873ba9c66e6d86ee342 admin-user: y00122496 (password is 3b68ee) D:\mfossil open ops D:\mdir 1client.txt D:\mfossil add client.txt ADDED client.txt D:\mfossil commit --comment Client1 Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 130 1 0 0 Received: 78 2 0 0 Total network traffic: 321 bytes sent, 289 bytes received New_Version: d2341c76226d722de9c43c1d05303fe5430a4407 Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 447 7 0 0 Received: 172 4 0 0 Total network traffic: 410 bytes sent, 345 bytes received D:\mfossil ls -l UNCHANGED client.txt Turn to server D:\mcd /d D:\o D:\ofossil open ops D:\ofossil ls -l client.txt is NOT in the repository of server D:\odir 1server.txt D:\ofossil add server.txt ADDED server.txt D:\ofossil commit --comment Server1 New_Version: a49b7975fad894b8c161165324c034667bccf8d7 D:\ofossil ls -l UNCHANGED server.txt Turn to client D:\ocd /d D:\m D:\mfossil sync http://y00122496:3f57fe@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 355 5 0 0 Received: 264 6 0 0 Sent: 541 9 0 0 Received: 952 8 2 0 Total network traffic: 872 bytes sent, 1084 bytes received D:\mfossil ls -l UNCHANGED client.txt server.txt is NOT in the repository of client D:\m The result means the client can clone the repository from server, but cannot sync from server, no matter pull or push. From: Ron Wilson [ronw.m...@gmail.com] Re: [fossil-users] Maybe a bug in sync On the server, you don't need to do a fossil open. The repository, in this
Re: [fossil-users] commit command seems to be slow
On Fri, Aug 05, 2011 at 02:14:46AM +, altufa...@mail.com wrote: Fossil is flexible here. yes/no, 1/0, on/off, true/false any of these can be used for binary settings. Some settings (like proxy) even can use real proxy address than on/off. very cool! Well, you can set a setting to 'potato', and you can be sure that it will be hard to forecast what it can do. You may set it to enable/disable, enabled/disabled, Yes/No, ... and who knows if it will do what you expect. For the amount of possibilities you mentioned, you have to know the subset of English that fossil understands by knowing the source code. If find this a bit misleading. If I said fossil settings mtime-changes enabled, I'd like it to tell me: please say on or off (or whatever single agreement we come up with). I don't mind any of the names, but I'd like ot be one pair and enforced. That's my vote. :) - Original Message - From: Wes Freeman Sent: 08/04/11 09:32 PM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] commit command seems to be slow 2011/8/4 Lluís Batlle i Rossell virik...@gmail.com: On Thu, Aug 04, 2011 at 05:21:00PM +0200, Stephan Beal wrote: 2011/8/4 Lluís Batlle i Rossell virik...@gmail.com (btw, I never know what do I have to write to enable. 'on', '1', 'yes', ... and what to disable) Try 'fossil set' and use whatever it shows. 1 and 0 work for me. It shows whatever you set it to, or nothing. :) How about fossil help set. It shows the defaults. Wes ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
On 08/05/2011 11:38 AM, Lluís Batlle i Rossell wrote: If find this a bit misleading. If I said fossil settings mtime-changes enabled, I'd like it to tell me: please say on or off (or whatever single agreement we come up with). I don't mind any of the names, but I'd like ot be one pair and enforced. That's my vote. :) Definitely agree! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
On Aug 5, 2011, at 10:38 , Lluís Batlle i Rossell wrote: On Fri, Aug 05, 2011 at 02:14:46AM +, altufa...@mail.com wrote: Fossil is flexible here. yes/no, 1/0, on/off, true/false any of these can be used for binary settings. Some settings (like proxy) even can use real proxy address than on/off. very cool! Well, you can set a setting to 'potato', and you can be sure that it will be hard to forecast what it can do. You may set it to enable/disable, enabled/disabled, Yes/No, ... and who knows if it will do what you expect. For the amount of possibilities you mentioned, you have to know the subset of English that fossil understands by knowing the source code. If find this a bit misleading. If I said fossil settings mtime-changes enabled, I'd like it to tell me: please say on or off (or whatever single agreement we come up with). I don't mind any of the names, but I'd like ot be one pair and enforced. That's my vote. :) ++ So why not potato/cucumber? ;) Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
Le 2011-08-05 à 04:38, Lluís Batlle i Rossell virik...@gmail.com a écrit : On Fri, Aug 05, 2011 at 02:14:46AM +, altufa...@mail.com wrote: Fossil is flexible here. yes/no, 1/0, on/off, true/false any of these can be used for binary settings. Some settings (like proxy) even can use real proxy address than on/off. very cool! Well, you can set a setting to 'potato', and you can be sure that it will be hard to forecast what it can do. You may set it to enable/disable, enabled/disabled, Yes/No, ... and who knows if it will do what you expect. For the amount of possibilities you mentioned, you have to know the subset of English that fossil understands by knowing the source code. If find this a bit misleading. If I said fossil settings mtime-changes enabled, I'd like it to tell me: please say on or off (or whatever single agreement we come up with). I don't mind any of the names, but I'd like ot be one pair and enforced. That's my vote. :) Agree too, it can force you to use one pair of word when you set it, but I think it should still recognize same as before for settings that are already set. Otherwise such update could frustrate a few user that didn't notice this change. -- Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
On Fri, Aug 5, 2011 at 1:22 PM, Remigiusz Modrzejewski l...@maxnet.org.plwrote: ++ So why not potato/cucumber? ;) My Comp-sci teacher back in the 80's always used the word broccoli for such cases. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] [OT] commit command seems to be slow
On Aug 5, 2011, at 15:14 , Stephan Beal wrote: ++ So why not potato/cucumber? ;) My Comp-sci teacher back in the 80's always used the word broccoli for such cases. Heh, Broccoli is a name of some big project my team finished just before I joined ;) Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
On Aug 5, 2011, at 15:13 , Martin Gagnon wrote: If find this a bit misleading. If I said fossil settings mtime-changes enabled, I'd like it to tell me: please say on or off (or whatever single agreement we come up with). I don't mind any of the names, but I'd like ot be one pair and enforced. That's my vote. :) Agree too, it can force you to use one pair of word when you set it, but I think it should still recognize same as before for settings that are already set. Otherwise such update could frustrate a few user that didn't notice this change. I'd say there's a better solution. It should recognize all current words, but normalize them to a single pair. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
On Fri, Aug 5, 2011 at 9:38 AM, Remigiusz Modrzejewski l...@maxnet.org.plwrote: On Aug 5, 2011, at 15:13 , Martin Gagnon wrote: If find this a bit misleading. If I said fossil settings mtime-changes enabled, I'd like it to tell me: please say on or off (or whatever single agreement we come up with). I don't mind any of the names, but I'd like ot be one pair and enforced. That's my vote. :) Agree too, it can force you to use one pair of word when you set it, but I think it should still recognize same as before for settings that are already set. Otherwise such update could frustrate a few user that didn't notice this change. I'd say there's a better solution. It should recognize all current words, but normalize them to a single pair. Kind regards, Remigiusz Modrzejewski I agree, it seems to be best solution. Now, what's about this slow commit issue... -- Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
On Aug 5, 2011, at 16:06 , Martin Gagnon wrote: Now, what's about this slow commit issue... Wasn't that resolved by setting mtime-based changes? Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] commit command seems to be slow
Le 2011-08-05 à 10:17, Remigiusz Modrzejewski l...@maxnet.org.pl a écrit : On Aug 5, 2011, at 16:06 , Martin Gagnon wrote: Now, what's about this slow commit issue... Wasn't that resolved by setting mtime-based changes? Extra command should not behave the same? -- Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] 答复: fossil-users Digest, Vol 43, Issue 3
There could be one bug, if what you're showing is the actual output of the terminal. The reason I say that is the following: D:\ofossil open ops D:\ofossil ls -l * In between those two lines, you should get fossil's output that says client.txt project-name: unnamed repository:... several more lines comment: Client1 (user: .,..)* So if you don't see the above, then something is wrong with fossil open for some reason (perhaps an errant _FOSSIL_ or something similar). Following your test generally by hand on my fossil (1.19: fca3073721 from 7/22) gives the expected response. However, there is one other error in what you are expecting to happen. When you issue D:\mfossil sync http://y00122496:3f57fe@y00122496:8080 you are *only* syncing the repository. You are not updating the current checkout to the newest commit. So you need to issue a fossil update command for the 'client' to see the servers changes. Note that this doesn't apply the other way, because when you issue 'fossil open' it checks out the newest commit. So, that part works perfectly fine. It seems that the fossil open is what is messing things up. If you don't see *any* output of that, that is probably where the error is. I would suggest issuing all the commands by hand an ensuring that the output is as expected. Tomek 2011/8/5 Yujianbin yujian...@huawei.com Hi, Ron: Thanks a lot! I think with or without open repository 'ops' in server, the server should act equally. This is the test: Content of tst_server.bat md D:\o cd /d D:\o if exist ops del /q ops if exist _FOSSIL_ del /q _FOSSIL_ fossil version @echo. @echo Please record the password and set it into tst_client.bat fossil new ops fossil server ops The result of run tst_server.bat is in tst_server.txt: D:\tst_server D:\md D:\o D:\cd /d D:\o D:\oif exist ops del /q ops D:\oif exist _FOSSIL_ del /q _FOSSIL_ D:\ofossil version This is fossil version 1.18 [df9da91ba8] 2011-07-13 23:03:41 UTC Please record the password and set it into tst_client.bat D:\ofossil new ops project-id: 23192a3021d29562f65a705ddc8dba8016070a32 server-id: ea446b3b950372ff8114dfb3e570cada9597beec admin-user: y00122496 (initial password is 3f57fe) D:\ofossil server ops Listening for HTTP requests on TCP port 8080 Type Ctrl-C to stop the HTTP server Then copy the password into tst_client.bat as follow: md D:\m cd /d D:\m if exist ops del /q ops if exist _FOSSIL_ del /q _FOSSIL_ fossil clone http://y00122496:3f57fe@y00122496:8080 ops fossil open ops dir client.txt fossil add client.txt fossil commit --comment Client1 fossil ls -l @echo. @echo Turn to server cd /d D:\o fossil open ops fossil ls -l @echo. @echo client.txt is NOT in the repository of server dir server.txt fossil add server.txt fossil commit --comment Server1 fossil ls -l @echo. @echo Turn to client cd /d D:\m fossil sync http://y00122496:3f57fe@y00122496:8080 fossil ls -l @echo. @echo server.txt is NOT in the repository of client The result of run tst_client.bat is in tst_client.txt: D:\q\fossil\tst_client D:\md D:\m D:\cd /d D:\m D:\mif exist ops del /q ops D:\mif exist _FOSSIL_ del /q _FOSSIL_ D:\mfossil clone http://y00122496:3f57fe@y00122496:8080 ops Bytes Cards Artifacts Deltas Sent: 53 1 0 0 Received: 344 5 1 0 Sent: 58 2 0 0 Received: 634 2 0 0 Total network traffic: 491 bytes sent, 1129 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 23192a3021d29562f65a705ddc8dba8016070a32 server-id: ff80810a3b3b768c1dec8873ba9c66e6d86ee342 admin-user: y00122496 (password is 3b68ee) D:\mfossil open ops D:\mdir 1client.txt D:\mfossil add client.txt ADDED client.txt D:\mfossil commit --comment Client1 Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 130 1 0 0 Received: 78 2 0 0 Total network traffic: 321 bytes sent, 289 bytes received New_Version: d2341c76226d722de9c43c1d05303fe5430a4407 Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas
Re: [fossil-users] 答复: fossil-users Digest, Vol 43, Issue 3
One other thought occured to me, which is the possibility that your server is not actually running on :8080, because you have several fossil servers open. You might want to check this possibility as well. Tomek 2011/8/5 Tomek Kott tkott.s...@gmail.com There could be one bug, if what you're showing is the actual output of the terminal. The reason I say that is the following: D:\ofossil open ops D:\ofossil ls -l * In between those two lines, you should get fossil's output that says client.txt project-name: unnamed repository:... several more lines comment: Client1 (user: .,..)* So if you don't see the above, then something is wrong with fossil open for some reason (perhaps an errant _FOSSIL_ or something similar). Following your test generally by hand on my fossil (1.19: fca3073721 from 7/22) gives the expected response. However, there is one other error in what you are expecting to happen. When you issue D:\mfossil sync http://y00122496:3f57fe@y00122496:8080 you are *only* syncing the repository. You are not updating the current checkout to the newest commit. So you need to issue a fossil update command for the 'client' to see the servers changes. Note that this doesn't apply the other way, because when you issue 'fossil open' it checks out the newest commit. So, that part works perfectly fine. It seems that the fossil open is what is messing things up. If you don't see *any* output of that, that is probably where the error is. I would suggest issuing all the commands by hand an ensuring that the output is as expected. Tomek 2011/8/5 Yujianbin yujian...@huawei.com Hi, Ron: Thanks a lot! I think with or without open repository 'ops' in server, the server should act equally. This is the test: Content of tst_server.bat md D:\o cd /d D:\o if exist ops del /q ops if exist _FOSSIL_ del /q _FOSSIL_ fossil version @echo. @echo Please record the password and set it into tst_client.bat fossil new ops fossil server ops The result of run tst_server.bat is in tst_server.txt: D:\tst_server D:\md D:\o D:\cd /d D:\o D:\oif exist ops del /q ops D:\oif exist _FOSSIL_ del /q _FOSSIL_ D:\ofossil version This is fossil version 1.18 [df9da91ba8] 2011-07-13 23:03:41 UTC Please record the password and set it into tst_client.bat D:\ofossil new ops project-id: 23192a3021d29562f65a705ddc8dba8016070a32 server-id: ea446b3b950372ff8114dfb3e570cada9597beec admin-user: y00122496 (initial password is 3f57fe) D:\ofossil server ops Listening for HTTP requests on TCP port 8080 Type Ctrl-C to stop the HTTP server Then copy the password into tst_client.bat as follow: md D:\m cd /d D:\m if exist ops del /q ops if exist _FOSSIL_ del /q _FOSSIL_ fossil clone http://y00122496:3f57fe@y00122496:8080 ops fossil open ops dir client.txt fossil add client.txt fossil commit --comment Client1 fossil ls -l @echo. @echo Turn to server cd /d D:\o fossil open ops fossil ls -l @echo. @echo client.txt is NOT in the repository of server dir server.txt fossil add server.txt fossil commit --comment Server1 fossil ls -l @echo. @echo Turn to client cd /d D:\m fossil sync http://y00122496:3f57fe@y00122496:8080 fossil ls -l @echo. @echo server.txt is NOT in the repository of client The result of run tst_client.bat is in tst_client.txt: D:\q\fossil\tst_client D:\md D:\m D:\cd /d D:\m D:\mif exist ops del /q ops D:\mif exist _FOSSIL_ del /q _FOSSIL_ D:\mfossil clone http://y00122496:3f57fe@y00122496:8080 ops Bytes Cards Artifacts Deltas Sent: 53 1 0 0 Received: 344 5 1 0 Sent: 58 2 0 0 Received: 634 2 0 0 Total network traffic: 491 bytes sent, 1129 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 23192a3021d29562f65a705ddc8dba8016070a32 server-id: ff80810a3b3b768c1dec8873ba9c66e6d86ee342 admin-user: y00122496 (password is 3b68ee) D:\mfossil open ops D:\mdir 1client.txt D:\mfossil add client.txt ADDED client.txt D:\mfossil commit --comment Client1 Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 130 1 0
Re: [fossil-users] [OT] commit command seems to be slow
Ha, never thought there can be fun in this list! :D - Original Message - From: Remigiusz Modrzejewski Sent: 08/05/11 07:07 PM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] [OT] commit command seems to be slow On Aug 5, 2011, at 15:14 , Stephan Beal wrote: ++ So why not potato/cucumber? ;) My Comp-sci teacher back in the 80's always used the word broccoli for such cases. Heh, Broccoli is a name of some big project my team finished just before I joined ;) Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
