Re: [fossil-users] A-B comparison of proposed timeline changes
On 2017-11-24 9:35, Richard Hipp wrote: Which is better? A: https://www.fossil-scm.org/a/timeline B: https://www.fossil-scm.org/b/timeline They both use too much vertical screen space, IMO. Also: A: https://www.fossil-scm.org/a/finfo?name=src/search.c B: https://www.fossil-scm.org/b/finfo?name=src/search.c B is much better, IMO. Just as clear and less vertical space waste. Wasting space vertically has become a huge problem in UI designs for me the last few years. The change here is to emphasis the check-in comment and de-emphasize the links to the check-in details and other information. That's a good objective, and I like the examples about equally from that standpoint. -- Doug "Lefty" Franklin NutDriver Racing http://NutDriver.org Facebook: NutDriver Racing Sponsored by Murphy ___ 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] Apparently a bug in ticketing
On 2017-05-24 21:27, Andy Bradford wrote: If you can reproduce it, perhaps a video showing all your commands or interactions with the UI would also reveal something? Yeah. :) Unfortunately, I haven't gotten the scenario narrowed down that much. I'll keep trying to create a reproduction scenario. The only thing I'm positive is common between the two instances is that I was creating new tickets in succession, moments apart in the UI. -- Doug "Lefty" Franklin NutDriver Racing http://NutDriver.org Facebook: NutDriver Racing Sponsored by Murphy ___ 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] Apparently a bug in ticketing
On 2017-05-23 21:21, Andy Bradford wrote: Thus said Doug Franklin on Mon, 22 May 2017 18:32:00 -0400: 11. Oops. I don't have three tickets. I have two tickets. The first ticket is fine. The original second ticket seems to be gone (it's not in the "All tickets" list), and the current second ticket has all of the values of the third ticket, but it has the user comment from the original second ticket as its first user comment, and the comment entered for the third ticket as its second user comment. Also, regarding the differing users. How is this possible? Are you logging into Fossil UI using more than one user? What are you doing to create tickets using multiple users? These facts were not mentioned in steps 4--10. Sorry, Andy, that was me not being clear. I should've put "user comment" in quotation marks because I was talking about the field on the form labeled "User Comment". It was three tickets created by one user (there's only one actual user, me), one right after the other. I'll rephrase to be more clear: "... and the second ticket has all of the values of the third ticket, but it has the "User Comment" text from the original second ticket as its first "User Comment", and the "User Comment" intended for the third ticket is now the second "User Comment" of the second ticket." And I don't expect you'll easily be able to recreate it. I've tried numerous times on pristine repositories created just to recreate the problem. But I haven't been able to hit the right combination yet. And, if it would help, I can share the repos ... maybe as a gist on github ... -- Doug "Lefty" Franklin NutDriver Racing http://NutDriver.org Facebook: NutDriver Racing Sponsored by Murphy ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Apparently a bug in ticketing
This is the second repository this has happened on, with two different Fossil versions. The first time, it happened on a large repository of stuff I couldn't share, and on a 1.x version of Fossil. Now, it's happened on a small repos filled with stuff I can share. What I did to get where I am: 1. Created a repos. 2. Pulled in some files. 3. Did a few checkins and wiki edits (there are 89 timeline entries of all types). 4. Started adding tickets. 5. Clicked "New ticket" from the "All tickets" view. 6. First ticket created fine. 7. Clicked "New ticket" from the view of the first ticket. 8. Second ticket created fine. 9. Clicked "New ticket" from the view of the second ticket. 10. Filled in the form and clicked submit. 11. Oops. I don't have three tickets. I have two tickets. The first ticket is fine. The original second ticket seems to be gone (it's not in the "All tickets" list), and the current second ticket has all of the values of the third ticket, but it has the user comment from the original second ticket as its first user comment, and the comment entered for the third ticket as its second user comment. Fossil 2.2 [81d7d3f43e] 2017-04-11 20:54:55 running on Linux Mint 18. As soon as I noticed it, I copied off the repository file. It's about 1.8M bytes. This hasn't happened on every repository I have, but once it happened the first time I got gun shy and I haven't been using tickets as much. -- Doug "Lefty" Franklin NutDriver Racing http://NutDriver.org Facebook: NutDriver Racing Sponsored by Murphy ___ 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] Problem with: fossil revert -r xxx
On 2017-05-11 7:03, Richard Hipp wrote: Yeah. In fact, I didn't even remember that there was a 'revert' command. And even now, I'm not entirely clear what it does, or what it is intended to do. I use it a few times a year when I thoroughly mess up a file or two locally and need to go back to the version in the repos. I could delete the file and "fossil update", but "fossil rev $filename" is one stop shopping. -- Doug "Lefty" Franklin NutDriver Racing http://NutDriver.org Facebook: NutDriver Racing Sponsored by Murphy ___ 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] WARNING: multiple open leaf check-ins on trunk:
On 2015-05-29 19:19, Ron W wrote: I suspect, in most case, multiple independent branches with the same name are not a problem. But trunk is a special case that may warrant a warning. I don't think I'd take that suspicion to the bank. Personally, I think it should warn on duplication of an existing tag or branch name, with a --force option if you know what you're doing. :) [Grin because I hose myself most often when I'm sure I'm doing the right thing.] -- Thanks, DougF (KG4LMZ) ___ 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] Skin almost finished.
On 2015-05-01 4:43, Martin S. Weber wrote: This is more user-friendly than deciding an optimal reading width for them (that may or may not pay attention to user-styles, user-selected fonts, one of the ways a document can be scaled on the user-end, etc.), so here's a tip to the hat for you: *. +100 People have different hardware; use their systems differently; configure their systems differently; run different sets of applications. Let users decide how big the window should be for their usage and preferences, both for browsers and for GUI apps. -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Associating an existing checking with an existing ticket
Howdy, folks, If I forget to insert the UUID for a ticket into the checkin/commit comment, can I go back later and associate that checkin/commit with that ticket? I can create a new comment for the ticket that includes the UUID of the checkin, but that doesn't get Fossil to recognize the association. That is, the checkin doesn't show up in the Associated checkins list, even after adding the comment to the ticket. Perhaps some tagging I could do from the command line? -- Thanks, DougF (KG4LMZ) ___ 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] Excessively long path length breaks working copy on Windows 7
On 2014-11-17 9:31, org.fossil-scm.fossil-us...@io7m.com wrote: That's still only 234 characters. I'm not entirely sure why I'm apparently hitting this limit at all. This is easily reproduceable, just create the above (relative) path on a non-Windows machine and then check out on a Windows 7 machine. It could be that there's a conversion to a UNC path in there somewhere. If so, the name would be expanded to something like \\MYMACHINE\DRIVE\PATH\ON\THE\DRIVE and might exceed the Windows limits. Though I thought those limits had gone up to something around 1,000 characters (bytes?) when NTFS came along. -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Strange Problem
Howdy, folks, I've got a small repository that I built using Fossil 1.25 that is called the LocalEnv repository. I access it over CGI to a local server, logged in as a supervisor user. It's almost all Markdown wiki pages pulled from /doc/tip and a couple of logo graphics files. The wiki's home page is stored in /doc/tip/home.md. A little while ago, I accidentally edited it in WYSIWIG mode instead of Markdown mode and saved the changes. Now, when I choose the Wiki option on the main menu, I have two home page entries: * /doc/tip/home.md wiki home page. * LocalEnv project home page. The second one has always been there, but the first one is new. When I choose the first one, it takes me back to the home page, but with no sub menu to allow editing the home page. When I choose the second one, it takes me to an empty page having a submenu with Edit and History entries. Also, the repo was configured to allow WYSIWIG editing, but now it's not. I went to the new home page and deleted the contents got an actually empty page with a complete submenu (Append, Attach, Details, Diff, Edit, History). That didn't fix the problem, though. I still have two home page entries in the Wiki page, and I still can't get a submenu on the home page through the WWW interface. I'd love to hear suggestions on debugging what went wrong so I can figure out how to fix it. I tried going back to the Admin - Configuration page and resetting the Index Page, but that didn't help. I also tried re-enabling Allow WYSIWIG Editing, but that also didn't help. -- Thanks, DougF (KG4LMZ) ___ 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] Strange Problem
On 2014-11-04 10:03, Stephan Beal wrote: i don't have an immediate suggestion other than to first try a newer version. 1.25 is about 18 months old [...] Sorry, I left that out of my email. I created the repo under 1.25. A couple of weeks ago I upgraded that server to Fossil 1.29. Everything worked fine until that inadvertent edit of the home page in WYSIWIG mode. Which reminded me of fossil rebuild, which fixed me up nicely! Sorry for the noise, I should've remembered fossil rebuild sooner. -- Thanks, DougF (KG4LMZ) ___ 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] syncing many repositories
On 2014-08-09 12:48, org.fossil-scm.fossil-us...@io7m.com wrote: I don't suppose there's any way to make fossil hit a given URI whenever the current repository receives artifacts? Could the recently discussed RSS feature help, at least to provide notifications of updates on the public side? -- Thanks, DougF (KG4LMZ) ___ 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 CLI tricks: interrupting a commit message
On 2014-06-17 22:00, Andy Goth wrote: This almost works in csh (which I am regrettably forced to use). Yes, the command is not executed but is still stuffed in the history buffer, Maybe I'm OCD or something, but if I have to do it more than twice, it gets embodied as a script. :) -- Thanks, DougF (KG4LMZ) ___ 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] Location of .fossil Database
On 2014-05-21 12:49, Stephan Beal wrote: We all have our quirks. One of mine is that i refuse to come into physical contact with an Apple product of any sort, do not provide any tech support of any kind for Apple products, nor do i allow Apple products in my flat. (Why i do that is not relevant here, i'm just pointing out that we are all pedantic about something or other.) I'm the same way about magazine disconnector safeties. :) -- Thanks, DougF (KG4LMZ) ___ 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] can fossil try harder on sync failure?
On 2014-05-08 16:18, Rich Neswold wrote: On Wed, May 7, 2014 at 12:59 AM, Andy Bradford amb-sendok-1402034378.gfecjnjggaibliman...@bradfords.org wrote: Thus said Rich Neswold on Wed, 16 Apr 2014 15:40:23 -0500: It would be nice if fossil would break the pull into smaller transactions which contain valid timeline commits so, if there's a database timeout, the next time I try to pull it can continue where it left off. Does SQLite support nested transactions? If so, that would seem to be worth considering. -- Thanks, DougF (KG4LMZ) ___ 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] ticket editing
On 2014-03-17 5:53, j. van den hoff wrote: it is really a nuisance to look at a seriously misleading/erroneous/misplaced ticket comment (the more so, if it happens not to be the very last one) and not being able to correct it. I just close the broken ticket and start a new one. I even add a Bad Ticket resolution so those cases can be filtered in or out. -- Thanks, DougF (KG4LMZ) ___ 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] Missing highlighted space changes in diff?
On 2014-03-05 6:39, Stephan Beal wrote: By removing the if, Joel changed the semantics (not only the indentation) of the code. i would argue that he is indeed the one who should be blamed in that case. In Python, changing that indentation does indeed change the semantics. It changes which block contains the line. -- Thanks, DougF (KG4LMZ) ___ 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] Memorable names for ticket IDs
On 2013-09-06 20:11, Ross Berteig wrote: ba-ba-ba-ba 12345678di-ku-poo-wa 74a95e62vu-che-roo-si da39a3ee5e6b4b0d3255bfef95601890afd80709 ghi-le-clo-phoo-roo-to-no-cy-ki-py-frau- phau-bly-sa-fa-bla-chau-gha-bau-ce That last one is too long for easy comprehension or handling. But the four syllable ones for four bytes work reasonably well. Odd numbers of digits could possibly be handled by having a separate set of sixteen syllables used only in the case of a trailing odd hex digit, or forcing sixteen specific syllables to be used in that case. -- Thanks, DougF (KG4LMZ) ___ 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] Memorable names for ticket IDs
On 2013-09-05 13:43, Ross Berteig wrote: First off, as you mentioned a few posts ago, you've got to get it examining the bits in the same order and chunks regardless of the endianness of the host. At that point, it seems like prefixing ought to start working as expected. I'm not convinced we ever need to generate the memorable name from any less information than the entire hash. These are going to get long, fast, as someone else already noted. However, in the past I've seen algorithms to generate random words that are still pronounceable, one character at a time. The trouble here is likely to be the comparative lack of vowels. Perhaps an algorithm generating words and/or phrases from syllables instead of characters. And perhaps some algorithm along those lines could mashup with the code you already have to produce prefixable, pronounceable, memorable phrase tokens for the hashes, that don't end up too long for people to want to deal with them. -- Thanks, DougF (KG4LMZ) ___ 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] commits from host A sometimes not seen on B
On 2013-08-19 20:31, Richard Hipp wrote: That option is unreleased, so you'll have to compile from sources. That is easier than you might imagine. Instructions here: http://www.fossil-scm.org/fossil/doc/trunk/www/build.wiki It /must/ be. Even /I/ managed it! :) -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fwd: It's Probably Permissions
Original Message Subject: It's Probably Permissions Date: Sun, 16 Jun 2013 19:42:56 -0400 From: Doug Franklin nutdriverle...@comcast.net I'm trying for the first time to get Fossil hooked up via CGI with my tame Apache server. [...] So, I found the problem ... At Richard's suggestion, I got rid of the soft links from, and removed, the /usr/share/fossil directory. The only reason it existed was to house soft links to user repositories in directories private to the user. That was to allow the Apache user to be able to serve private repositories without opening up user-private directory permissions. Then I changed the cgi-bin scripts for the repositories to reference the user-private directories directly. Opened up the permissions on the repository files. Still the same problem (can't open the -journal file). Once I gave world-write permission to the user-private directory housing the .fossil files, everything was hunky dory. Now I just have to dink around with the groups and such to tailor that breach of the user-private directories. Also, following Richard's suggestion, I tried accessing $SERVER/cgi-bin/$REPOSITORY/test-env, but it produced the same page that I got without /test-env on the URL. -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] It's Probably Permissions
Howdy, folks,
I'm trying for the first time to get Fossil hooked up via CGI with my
tame Apache server. It's running on 32-bit x86 Linux. It's a pretty
much bone stock Apache on Linux install, with modules alias and mod_cgi
installed. The scripts for my two Fossil repositories are the only thin
in the cgi-bin directory, even.
I've got two repositories. They live in my ~/fossil directory. The
actual repository files are both 644 permissions, owned my my user.
To hook them up to CGI, I created soft links from /usr/share/fossil to
each of the .fossil repository files in ~/fossil. These soft links are
owned by root. They currently have l777 permissions, probably as a
result of my dinking around trying to fix this issue.
Then I created two files in /usr/lib/cgi-bin, one for each repository.
/usr/lib/cgi-bin/DAV:
#!/usr/bin/fossil
repository: /usr/share/fossil/DAV.fossil
/usr/lib/cgi-bin/LocalEnv:
#!/usr/bin/fossil
repository: /usr/share/fossil/LocalEnv.fossil
These files have permissions 755 and are owned by root.
Accessing the DAV.fossil repository over CGI works just fine with the
URL http://$MYSERVER/cgi-bin/DAV and all operations appear to work as
expected.
However trying to access LocalEnv.fossil using
http://$MYSERVER/cgi-bin/LocalEnv results in a database error after
redirecting to $MYSERVER/cgi-bin/LocalEnv/doc/tip/home.md:
attempt to write a readonly database: {CREATE TABLE IF NOT EXISTS
vcache(vid INTEGER, fname TEXT, rid INTEGER, UNIQUE(vid,fname,rid))}
If I go to ~/fossil I can use fossil rebuild $REPOSITORY successfully.
If I go to /usr/share/fossil, I have to use sudo fossil rebuild
$REPOSITORY, but for both of them. That makes sense since root owns the
ones in /usr/share/fossil and my local user the ones in ~/fossil.
In each location, the cgi-bin scripts and the .fossil repository files
have the same permissions, but the DAV repository works and the LocalEnv
repository throws up errors over CGI.
The only difference I can think of, besides their contents, is that the
LocalEnv repository uses embedded documentation and uses
$HOST/cgi-bin/$REPOS/home/tips/home.md as the home page while the DAV
repository just lets everything default and uses the default
$HOST/cgi-bin/$REPOS/home URL.
Any suggestions would be gleefully appreciated!
--
Thanks,
DougF (KG4LMZ)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Missing Wiki Pages
Howdy, folks, I don't know about anyone else, but I would find it quite useful to have a command to list all the missing wiki pages, in addition to the existing command to show all wiki pages. In other words, it would show any wiki page links from existing wiki pages that do not have a target wiki page. This would help catching typos in wiki page links, and it would help people like me who create documents outward in (top-bottom and bottom-top at the same time, meeting somewhere in the middle, eventually, hopefully). -- Thanks, DougF (KG4LMZ) ___ 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] custom priorities in ticket system
On 2013-06-07 16:53, Chad Perrin wrote: How would I go about adding a blocking severity or priority to Fossil's ticketing system (aka bugtracker)? Is there some other approach to solving the problem of identifying an issue as blocking that people use, that has not occurred to me? From the Web UI, Admin - Tickets - Common from there you can change the sets of values used for all of the enumerations in the ticketing system. The severity_choices and priority_choices declarations sound like the ones you seek. -- Thanks, DougF (KG4LMZ) ___ 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] Did you know that Fossil could do...
On 2013-05-28 9:08, Richard Hipp wrote: Survey: How many people know that in the web-based timeline for Fossil, you can click on any two nodes in the graph and get a diff between those two nodes? I think this is a very useful feature. But I'm guessing that not many people know it exists. Please confirm or refute my guess. Not me, but I'm pretty new to Fossil. And assuming I'm guessing correctly, do you have any suggestions on how I can get the word out about this and other useful but obscure features of Fossil? Hmmm. Maybe a fortune when the program starts up? Each fortune gives a teaser for one of these features and tells the operator how to get more detailed information, say, from the web site? -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Markdown
Do the default (downloadable) versions of Fossil not have Markdown support enabled, or am I doing something wrong? My browser keeps telling me open or save this unknown file type. -- Thanks, DougF (KG4LMZ) ___ 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] Ticket 'subsystem' field?
On 2013-03-24 17:40, Lluís Batlle i Rossell wrote: On Sun, Mar 24, 2013 at 09:37:41PM +, org.fossil-scm.fossil-us...@io7m.com wrote: Hello. I can set the subsystem field of a given ticket to XYZ with fossil ticket set X subsystem XYZ, but I can't seem to work out how to populate the drop down subsystem menu in the web interface. Is this documented anywhere? I sort of expected entries to appear there after I'd set the fields of a few tickets, but they didn't. Menu Admin, Tickets, Common. Edit the values in the subsystem_choices group. -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fwd: Configuration Export/Import
Original Message Subject: [fossil-users] Configuration Export/Import Date: Sat, 23 Feb 2013 12:18:19 -0500 From: Doug Franklin nutdriverle...@comcast.net However, I normally work in a cloned and autosynced copy of that repository. The clone lives on Windows XP. When I export the configuration from the clone on XP, the output file does not have any of my customizations, and only one user. Well, I think the reply to this StackOverflow question answers mine, too, I just didn't find it before posting here. :) http://stackoverflow.com/questions/13285099/common-header-and-footer-in-fossil?rq=1 I'm just asking something of it that it doesn't supply. -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Configuration Export/Import
Howdy, folks, I'm pretty new to fossil (less than a month), but I'm a veteran of other SCM systems, and I've quickly gotten Fossil pretty well tuned in to the way I want to work. So I tried using the configuration export and configuration import commands to make a template configuration. It worked just fine when I did it on Linux, including all of my customizations. However, I normally work in a cloned and autosynced copy of that repository. The clone lives on Windows XP. When I export the configuration from the clone on XP, the output file does not have any of my customizations, and only one user. I'm using the version 1.25 binaries posted to fossil-scm.org a few days ago. I created the repository with the 1.24 binaries from last October, also downloaded from fossil-scm.org. Does this sound like a bug, or like I'm doing something wrong? It seems pretty difficult to mess up fossil open REPOS, fossil conf export all FILE, but I've messed up simpler stuff before. I'd also like to suggest that the configuration export/import process not bring over the password hashes of users. I'd suggest that export not emit the pw hashes at all, and that import ignore them if present. Import would create a default password for any new users, and display it, like it does for the new and init commands. Passwords for existing users would be left alone. If I can get some time, I'll poke around in the source and see if I can come up with a patch. -- Thanks, DougF (KG4LMZ) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
