Re: [fossil-users] How to change 'binary' to non-binary?
On Tuesday 19 October 2010 15:52:48 Richard Hipp wrote: The diff limitation only comes up when you try to merge. You must be doing something more than backing things up. Ah, no; it was my mistake. I thought my fossil repo was growing too quickly (as in, simply putting the new version of the SQL file in as-is). But that was a mistaken perception on my part. So, never mind ... -- For privacy, my GPG key signature is: AD29415D signature.asc Description: This is a digitally signed message part. ___ 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 enhancements: Please test
Hi, 19/10/2010 23:59, Richard Hipp wrote: There is a file-format enhancement to Fossil that seeks to make Fossil run more efficiently on projects with a large number of files in each checkout. Help in testing this enhancement will be appreciated. [snip] It will be very helpful if you can try out this experimental Fossil and report both successes and failures. This is a great opportunity for you to contribute to the Fossil project even if you don't have the skills or desire to go code diving. [snip] Thanks for testing out the recent Fossil changes. Please be sure to report either success or failure (whichever you encounter) with the new Fossil to this mailing list, or directly to me at d...@sqlite.org mailto:d...@sqlite.org. I test it against a repo which has ~4780 files in it. No observable difference with version [8474ca6747]. (I only did some edit and commit.) Note: It seems detach command may useful in normal usage too; ie. you want history of repo but need to brake the heritage/sync from the real repo. -- D. Richard Hipp d...@sqlite.org mailto:d...@sqlite.org -- Regards, Hakki Dogusan ___ 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 enhancements: Please test
On Wed, Oct 20, 2010 at 5:32 AM, Hakki Dogusan dogus...@tr.net wrote: Hi, 19/10/2010 23:59, Richard Hipp wrote: There is a file-format enhancement to Fossil that seeks to make Fossil run more efficiently on projects with a large number of files in each checkout. Help in testing this enhancement will be appreciated. [snip] It will be very helpful if you can try out this experimental Fossil and report both successes and failures. This is a great opportunity for you to contribute to the Fossil project even if you don't have the skills or desire to go code diving. [snip] Thanks for testing out the recent Fossil changes. Please be sure to report either success or failure (whichever you encounter) with the new Fossil to this mailing list, or directly to me at d...@sqlite.org mailto:d...@sqlite.org. I test it against a repo which has ~4780 files in it. No observable difference with version [8474ca6747]. But it works, right? The performance bottleneck was coming up on a fossil rebuild command on repository with about 200,000 commits where each commit contained about 60,000 files. With older versions of Fossil, the rebuild was taking about 10 hours. We are hoping to get it down to the 5-10 minute range. Clearly the performance aspect is something that you cannot test easily. AT this point, I'm just wanting to make sure that all the old edit/commit infrastructure still works correctly. Another thing to check: For your new checkins on this repository, please go click on the link to the detailed information about that checkin, then click on the Manifest link. Does the manifest show all 4780 files in your check-in, or only those that changed? (I'm hoping it only shows those that changed.) Thanks for testing! (I only did some edit and commit.) Note: It seems detach command may useful in normal usage too; ie. you want history of repo but need to brake the heritage/sync from the real repo. -- D. Richard Hipp d...@sqlite.org mailto:d...@sqlite.org -- Regards, Hakki Dogusan ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ 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 enhancements: Please test
Hi, 20/10/2010 14:26, Richard Hipp wrote: On Wed, Oct 20, 2010 at 5:32 AM, Hakki Dogusan dogus...@tr.net mailto:dogus...@tr.net wrote: [snip] I test it against a repo which has ~4780 files in it. No observable difference with version [8474ca6747]. But it works, right? Yes, of course :) I only got a warning on open: WARNING: manifest checksum does not agree with disk Addendum: Files link crashes fossil.exe! Then it shows http://127.0.0.1:8080/dir?ci=tip; in address bar. (I checked with 'real' fossil.exe; Files link works there.) The performance bottleneck was coming up on a fossil rebuild command on repository with about 200,000 commits where each commit contained about 60,000 files. With older versions of Fossil, the rebuild was taking about 10 hours. We are hoping to get it down to the 5-10 minute range. Clearly the performance aspect is something that you cannot test easily. AT this point, I'm just wanting to make sure that all the old edit/commit infrastructure still works correctly. Another thing to check: For your new checkins on this repository, please go click on the link to the detailed information about that checkin, then click on the Manifest link. Does the manifest show all 4780 files in your check-in, or only those that changed? (I'm hoping it only shows those that changed.) Only changed ones showed. Thanks for testing! [snip] -- D. Richard Hipp d...@sqlite.org mailto:d...@sqlite.org -- Regards, Hakki Dogusan ___ 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 enhancements: Please test
On Wed, Oct 20, 2010 at 8:01 AM, Hakki Dogusan dogus...@tr.net wrote: I only got a warning on open: WARNING: manifest checksum does not agree with disk Addendum: Files link crashes fossil.exe! Then it shows http://127.0.0.1:8080/dir?ci=tip; in address bar. (I checked with 'real' fossil.exe; Files link works there.) Please try again using http://www.fossil-scm.org/fossil-w32-20101020123125.zip and let me know whether or not these problems have been fixed. Thanks! -- D. Richard Hipp d...@sqlite.org ___ 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 enhancements: Please test
Hi, 20/10/2010 15:34, Richard Hipp wrote: On Wed, Oct 20, 2010 at 8:01 AM, Hakki Dogusan dogus...@tr.net mailto:dogus...@tr.net wrote: I only got a warning on open: WARNING: manifest checksum does not agree with disk Addendum: Files link crashes fossil.exe! Then it shows http://127.0.0.1:8080/dir?ci=tip; in address bar. (I checked with 'real' fossil.exe; Files link works there.) Please try again using http://www.fossil-scm.org/fossil-w32-20101020123125.zip and let me know whether or not these problems have been fixed. Thanks! Both warning and crash gone with this version. Thank you! -- D. Richard Hipp d...@sqlite.org mailto:d...@sqlite.org -- Regards, Hakki Dogusan ___ 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] user capabilities - ui improvements?
Also, It is not clear for me the difference between: a - Admin: Create and delete users and s - Setup/Super-user: Setup and configure this website Is it really necessary to have these two separated options? They really confuse my co-workers and myself Ramon Ribó 2010/10/20 Wilson, Ronald rwils...@harris.com I’d like to make some observations of and suggestions for improving the ui admin of users. The User List screen is very clear; the notes with each capability as a letter spelled out is very neat and usable. However, when you click on a specific user, e.g. anonymous, the capabilities selection screen doesn’t show the letters anywhere and the list is in a different order from the letters. Also, some capabilities are renamed, e.g. on the user list, ‘h’ is for ‘hyperlinks’ whereas on the capabilities selection screen, I’m pretty sure ‘h’ is for ‘History’. Also, the default capabilities seem to imply that ‘developer’ inherits the capabilities of ‘reader’ (because the Password capability is not given to developer by default). This could be explained in the special logins section of the capabilities selection screen. All of this makes user administration a little cumbersome. I suggest that as a minimum, the capabilities selection screen should have the letters next to the checkboxes in that correspond to the letters defined on the user list screen. One last thing – just a question. Capability ‘b’ or Attach controls adding attachments to wiki or tickets. Does this depend on the capabilities ‘m’ (append-wiki) or ‘c’ (append-tkt) or ‘f’ (new-wiki) or ‘n’ (new-tkt)? I’d like to allow anonymous users to add attachments to tickets, but not wikis. Is that even possible? RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications™ NOTICE: This e-mail transmission (and any of its attachments) may contain confidential, proprietary and/or privileged information. The sender intends this transmission only for the designated recipient(s). If you are not a designated recipient (or authorized to receive for a designated recipient), you are hereby notified that the disclosure, copying, distribution or use of any of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please destroy this message, delete any copies which may exist on your system and notify the sender immediately. Thank you. ___ 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] user capabilities - ui improvements?
I just notices at the bottom of the user list there is note #4: 4. Users with privilege v inherit the combined privileges of developer, anonymous, and nobody. Well, 'v' is 'Developer' - so I'm thinking it wasn't really meant that developers should inherit the privileges of developer. Probably this is a typo and what was meant was this: 4. Users with privilege v inherit the combined privileges of reader, anonymous, and nobody. This would resolve one of my comments below. RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users- boun...@lists.fossil-scm.org] On Behalf Of Ramon Ribó Sent: Wednesday, October 20, 2010 10:29 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] user capabilities - ui improvements? Also, It is not clear for me the difference between: a - Admin: Create and delete users and s - Setup/Super-user: Setup and configure this website Is it really necessary to have these two separated options? They really confuse my co-workers and myself Ramon Ribó 2010/10/20 Wilson, Ronald rwils...@harris.com I'd like to make some observations of and suggestions for improving the ui admin of users. The User List screen is very clear; the notes with each capability as a letter spelled out is very neat and usable. However, when you click on a specific user, e.g. anonymous, the capabilities selection screen doesn't show the letters anywhere and the list is in a different order from the letters. Also, some capabilities are renamed, e.g. on the user list, 'h' is for 'hyperlinks' whereas on the capabilities selection screen, I'm pretty sure 'h' is for 'History'. Also, the default capabilities seem to imply that 'developer' inherits the capabilities of 'reader' (because the Password capability is not given to developer by default). This could be explained in the special logins section of the capabilities selection screen. All of this makes user administration a little cumbersome. I suggest that as a minimum, the capabilities selection screen should have the letters next to the checkboxes in that correspond to the letters defined on the user list screen. One last thing - just a question. Capability 'b' or Attach controls adding attachments to wiki or tickets. Does this depend on the capabilities 'm' (append-wiki) or 'c' (append-tkt) or 'f' (new-wiki) or 'n' (new-tkt)? I'd like to allow anonymous users to add attachments to tickets, but not wikis. Is that even possible? RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) NOTICE: This e-mail transmission (and any of its attachments) may contain confidential, proprietary and/or privileged information. The sender intends this transmission only for the designated recipient(s). If you are not a designated recipient (or authorized to receive for a designated recipient), you are hereby notified that the disclosure, copying, distribution or use of any of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please destroy this message, delete any copies which may exist on your system and notify the sender immediately. Thank you. ___ 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
[fossil-users] Jurassic Fossil backup question
Hi, I want to (properly) implement a backup feature in Jurassic. The rationale is, I want all my .fossil files to be copied to a (secure) directory. I think the fossil push command may be what I'm looking for, or is it better to simply copy the .fossil files? Thanks! ___ 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] Jurassic Fossil backup question
On Wed, 20 Oct 2010 18:03:21 +0200 (CEST), you wrote: Hi, I want to (properly) implement a backup feature in Jurassic. The rationale is, I want all my .fossil files to be copied to a (secure) directory. Every .fossil repository is a SQLite database file, you could use the .backup command of the SQLite command line tool (sqlite3), or the sqlite3_backup_*() C API. I think the fossil push command may be what I'm looking for, or is it better to simply copy the .fossil files? Copy is fine, unless someone changes the database at the same time, so you should lock the file somehow. -- ( Kees Nuyt ) c[_] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
