Re: [fossil-users] Simple edit of a wiki page name
Typically, one creates the correctly named page and abandons the original... From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Stephan Beal Sent: Wednesday, January 18, 2012 2:16 AM To: Fossil SCM user's discussion Subject: Re: [fossil-users] Simple edit of a wiki page name As the old song goes: "what's done cannot be undone, not here not in London." - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal On Jan 18, 2012 5:15 AM, "Matt Young" wrote: I Added a wiki page, I accept the changes then discover you want to edit the wiki page name. How does one do that? ___ 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] Needed: volunteer to autoconf Fossil
I don't expect it to be. From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Tuesday, June 14, 2011 10:35 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Needed: volunteer to autoconf Fossil On Tue, Jun 14, 2011 at 11:25 AM, Williams, Brian wrote: Has anyone thrown themselves on this grenade yet? If not, I can take a look at autoconf. I got a chat message from someone who said they would take a look. Surely the autoconf for Fossil won't be to hard? All it needs to do is check for a couple of libraries and set a few options based on --with-X flags. -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Remigiusz Modrzejewski Sent: Tuesday, June 14, 2011 7:12 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Needed: volunteer to autoconf Fossil On Jun 14, 2011, at 14:06 , Ben Summers wrote: > As an intermediate stage, a simple script to put the output of uname -s into the Makefile might be a way to get going? > > http://fossil-scm.org/index.html/timeline?r=configure-make > > autotools are a bit of a nightmare, and possibly overkill for a project which is so inherently portable and self-contained. Nope, there's need for more than just that - see the first post. You can try to get all that done without autohell, but I guess that shortly it will reach the same amount of pain. The only other way I see it is if Waf or some other nicer buildsystem could emit a configure shell script... Gour, can Waf do that? 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 -- 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] Needed: volunteer to autoconf Fossil
Has anyone thrown themselves on this grenade yet? If not, I can take a look at autoconf. -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Remigiusz Modrzejewski Sent: Tuesday, June 14, 2011 7:12 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] Needed: volunteer to autoconf Fossil On Jun 14, 2011, at 14:06 , Ben Summers wrote: > As an intermediate stage, a simple script to put the output of uname -s into the Makefile might be a way to get going? > > http://fossil-scm.org/index.html/timeline?r=configure-make > > autotools are a bit of a nightmare, and possibly overkill for a project which is so inherently portable and self-contained. Nope, there's need for more than just that - see the first post. You can try to get all that done without autohell, but I guess that shortly it will reach the same amount of pain. The only other way I see it is if Waf or some other nicer buildsystem could emit a configure shell script... Gour, can Waf do that? 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
Richard's question regarding a multi level undo, and when to purge, got me thinking; and I apologize for posting mid - thought stream ... What if fossil kept track of all the commands issued that change either the repository or the working files. Obviously, it already does this at some level (commits and merges); in the case of a revert (or even an update), it would save the affected files, perhaps by creating an automatic branch. Fossil now has the files but also the complete command path to reproduce a particular scenario, which would help in debugging. This would really fill any gap in the stated goal of never losing any work; not only committed work, but also work in progress. From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Sunday, May 22, 2011 5:51 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE! On Sun, May 22, 2011 at 12:04 AM, chi wrote: Ron Wilson schrieb: > On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa wrote: > >> On Sat, 21 May 2011 14:32:34 -0400 >> Richard Hipp wrote: >> >>> Does anybody have any other suggestions on how to prevent the lose >>> of uncommitted work? >> >> Maybe not suggestion to prevent losing of uncommitted work, but I'm >> thinking about using 'stash' in such situation. Perhaps Fossil could do this automatically. Whenever an 'update' would change any locally modified file, Fossil could stash the changes away first and inform the user. That's sort of what "fossil undo" does. Except it only stores the most recent change. You are suggesting an "auto-stash" that keeps backups at each change, and stores them in a visible place such as the stash. An interesting idea... Would we purge the auto-stash on a commit? Or just let it grow until the user manually purged it? -- 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] IMHO Fossil needs renaming...
Stephen, you hit on the point that was a revelation to me (back in the day). The Fossil web site isn't a web site; it's the WIKI. The discussions of page design aside, perhaps that fact should be mentioned in the first bullet. -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Stephen De Gabrielle Sent: Thursday, March 03, 2011 9:12 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] IMHO Fossil needs renaming... As, I hope, all list subscribers know, fossil is easily reskinnable. Being self-hosting, the fossil site is too. Can I suggest a competition with a few simple criteria & small reward - site should continue to be accessible for the sight impaired - CSS & HTML only. (extensive js can require more long term maintenance than is desirable) - should be accessable on a wide variety of devices (android/iPhone type smartphone browsers, tablets & netbooks 7?-10 inch both orientations, right up to my nice 24 inch screen) - should cope with users changing the browser font size, and setting low screen resolutions on small desktops/laptops - the logo should still be a fossil of some sort. Petrified wood and microscopic fossils allowed - changing the name is not an option. Winner gets the respect and admiration of their peers, runners up get included as selectable skins. What do you think? Stephen On Thursday, March 3, 2011, Kristoffer Lawson wrote: > > On 3 Mar 2011, at 13:41, Richard Hipp wrote: > >> >> >> On Thu, Mar 3, 2011 at 4:26 AM, Trou Macacq wrote: >> >> Design matters. >> >> >> Design != eye-candy > > Actually there is research to the opposite :-) > > When tested people quite literally find better looking services to be easier (not to mention more tempting, which should be obvious). The exact same functionality, or even worse functionality, when it looks good, is rated as being easier. > > I agree with the posters here that the main Fossil website could do with a bit of a touch up. If we were using Fossil I could possibly justify spending a few hours doing a bit of design on it myself. As it stands I wouldn't want to promise anything, although I'd be tempted to play around with it. > > For the record I don't think we need some full-blown Web 2.0 Ajax monster, with half of the functionality not working or taking forever to load. The Fossil website is simple, and is great for that reason. So I'd be looking more at a tummy tuck than anything too extensive. > > -- > Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/ > http://travellingsalesman.mobi - 1km & The world's most arctic startups > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- -- Stephen De Gabrielle stephen.degabrie...@acm.org Telephone +44 (0)20 85670911 Mobile+44 (0)79 85189045 http://www.degabrielle.name/stephen ___ 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] Fossil file deletion
I have a question for you: When you say you "copy" the repo, are you file coping or doing a fossil clone? Again, when you say you "overwrite" the repo on Computer 1, are overwriting the file or doing a sync? If you are really overwriting the repositories then I can well expect that there are problems. I have a similar setup, but I maintain a fossil repo on a thumb drive; when I get home, I do a sync with the repo on my home machine and I'm up to date. I update the workspace and I'm ready to work. Fossil is an extremely powerful and flexible tool, but it does have a few rules; one of those is to associate a check out with one (and only one) repository. -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Louis Hoefler Sent: Wednesday, February 16, 2011 9:19 AM To: fossil-users@lists.fossil-scm.org Subject: [fossil-users] Fossil file deletion Following szenario: I have two computers. On computer 1, I create a fossil with some work. Now I commit my work and copy the fossil to computer 2. I rename files on computer 2, do some other work, and commit. I make some filechanges on computer 1, and commit. Now I have two fossils who are out of sync. I come back home and overwrite the fossil from computer 1 with the one from computer 2 (where I renamed files). Now, after I do a fossil update, the (modified) files on computer 1 are deleted and fossil stops the update process, becouse it can not find the newly renamed files. I do not really understand the logic behind this error but, if this isnt the case: Files should be deleted only, if they have not changed (in case of a rename they should not be deleted if the last known version in fossil differs from the current file on disk). Greetings, Louis ___ 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
