Re: [fossil-users] Fossil behind proxy
On Sat, 2010-05-29 at 21:59 -0400, Richard Hipp wrote: > The http://www.sqlite.org/ and http://www.fossil-scm.org/ websites > are both run off of the same server ... This server takes over a > quarter million requests per day, 10GB of traffic/day, and it does > so using less than 3% of of the CPU on a virtual machine that is a > 1/20th slice of a real server. ... How much more efficient does that > need to be? Lots ... if it's CGI under Windows. Thank You, Paul Serice ___ 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] How to close a branch?
fossil tag --raw add closed ___ 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] Repository in a single file
On Sun, 2010-01-24 at 18:29 -0500, D. Richard Hipp wrote: > On Jan 24, 2010, at 5:42 PM, Paul Serice wrote: > > Just search for "Berkeley DB usage leading to respository > > corruption and data loss" on the Wikipedia page for Subversion. > > That's why subversion switched to SQLite, isn't it? They switched to pile-of-files as the default. They still have the option to create Berkeley DB repositories. From their INSTALL file, they use SQLite only internally which is probably a good thing because they've given Berkeley DB quite a black eye; whether it's deserved or not, I do not know. > Usually the whole drive goes out, rather than changing a single > byte. Well, your drive goes out, and you don't have a remote clone so you reach for your DVD backup which verified ok, but now when you restore, cpio warns about a checksum not matching. > But if you want to store backups as individual files (one file > per artifact) Andreas Kupries has created a fossil command to > do exactly that: "deconstruct". Nice. Thank You, Paul Serice ___ 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] Repository in a single file
On Sun, 2010-01-24 at 15:35 -0500, D. Richard Hipp wrote: > Could this be a case of "we've never done it that way before"? I think it's more a case of "been there, done that, never want to do it again." Just search for "Berkeley DB usage leading to respository corruption and data loss" on the Wikipedia page for Subversion. I think an analogous (and common experience) is losing most of a *.tar.gpg file because one byte early in the file is corrupt. (I think the same thing is true of *.tar.gz but not *.tar.bz2.) On the other hand, if your archive is just *.tar, one corrupt byte will cause you to lose at most up to the start of the next file in the archive. What's the story with SQLite? What's my exposure to a single corrupt byte? Thank You, Paul Serice ___ 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] Add files recursively?
> __FOSSIL__ is required, though you can rename it to ".fos" if you > don't want to look at it. This is dangerous because the following commands do very bad things: fossil extras --dotfiles fossil clean -f --dotfiles Thank You, Paul Serice ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil scripts
I've uploaded some scripts for fossil to the following URL: http://www.serice.net/fossil-scripts/ If there are more direct ways of doing these things, please let me know. The scripts are described below in alphabetical order: 1) fossil-branch [] - If a commit is not specified, show all the branches similar to how "git branch" shows them. If a commit is specified, show the branch where the commit resides. Example output looks like the following where "bar" is the current branch: * bar baz (closed) foo - The pseudo-commit "current" can be passed in as the first argument. If there isn't a real branch called "current", fossil-branch will print the name of the current branch. - It would be nice to be able to mark the private branches too, but I haven't been able to find an easy way to do this from the command line. 2) fossil-cat [] - Write the contents of the file associated with a particular commit to stdout. As a convenience, if is not specified, the commit is passed directly to "fossil artifact". 3) fossil-close-leaf - Close a leaf. 4) fossil-current - Prints the SHA-1 hash value for the current commit. 5) fossil-flatten - Generic script for flattening the log messages. It works by piping the log messages into it: alias ff="fossil-flatten" fossil leaves | ff - With all the scripts that flatten the log messages, a pager like the following should used inside a window wider than 80 columns: export PAGER="less -i -S -M -F" 6) fossil-help-all - Print the help for all commands listed in "fossil help". 7) fossil-log [ []] - Limit the log to display just the commits between and (inclusive). If is not an ancestor of , nothing is printed. If is not specified, it displays the commits starting with . If is not specified, it displays the commits starting with the current commit. This script also flattens so each is on a single line. 8) fossil-ls-tree [] - List the SHA-1 and file name for each file in . If is not specified, the current commit is used. 9) fossil-pending [] - Show the commits that are pending. This is typically used immediately after running "fossil pull". It lets you review the pending commits that will be applied to your branch by "fossil update". This is a wrapper around "fossil timeline descendants". In addition to flattening the log messages, it also filters out descendants that are on a different branch. 10) fossil-timeline ... - Simple wrapper around "fossil timeline". The main thing it does is flatten the log messages so each is on a single line making it easier to read if you have a sane pager. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
