Re: [fossil-users] G+ Fossil page?
On 20 Mar 2014, at 09:11, Martijn Coppoolse li...@martijn.coppoolse.com wrote: On 19-3-2014 18:28, Ron Wilson wrote: Does fossil need a G+ page (or FB page, or AOL page, for that matter) where that type of thing can be posted? i, for one, wouldn't mind manning a G+ community. I don't think Fossil *needs* a Google+ page; but it's always an extra channel for Fossil users. I’m afraid social media presence, from someone with a nontrivial number of followers, is something that is needed these days to gain any traction. (Or is there perhaps one i've missed so far? A cursory search revealed none.) There is also freecode.com http://freecode.com. Fossil has a listing there, but it is out of date. (http://freecode.com/projects/fossil) Does anybody know who the maintainer is? I happen to know. It’s me and DRH for the moment, according to Freecode. If someone wants, I can give write rights to that listing to more people here. Freecode seems to have an API, and so do Google+ and Facebook. It should be feasible to write a script that parses the downloads page for new versions, and publish the new version (including what's new) to those pages, no? No. Fossil announcements come in a structured list format, that is pretty long. Freecode announcements need to be just a few plain text sentences. There is no automated way to do this. That could make it easier to avoid forgetting a new release. Or we could just make sure it is done in the new release thread. Especially if we would collectively prepare a good release announcement. 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] looking for interesting new fossil skins
On 11 Feb 2014, at 19:42, Martijn Coppoolse li...@martijn.coppoolse.com wrote: Remigiusz Modrzejewski schreef op 11-2-2014 15:54: On 11 Feb 2014, at 15:42, Stephan Beal sgb...@googlemail.com wrote: i'm looking to clone someone's interesting fossil skin to snazz up my fossil repos a bit. Can any suggest a fossil repo with a nice skin? I once stole a skin I like, see here: http://dev.lrem.net/p2pvsim2/timeline I stole a similar one too; it was originally less 'advanced' (e.g. no blue background on mouseover of the menu items), which leads me to think that was the original. It was located at codingrobots.com, but that site no longer sports anything recognizable as fossil, though. And codingrobots.org redirects to a GitHub repo, so it looks as they've switched SCM. I think this is where I stole this one from. I don’t think I have done any work on them, so I probably just got a newer version. 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] looking for interesting new fossil skins
On 11 Feb 2014, at 15:42, Stephan Beal sgb...@googlemail.com wrote: i'm looking to clone someone's interesting fossil skin to snazz up my fossil repos a bit. Can any suggest a fossil repo with a nice skin? I once stole a skin I like, see here: http://dev.lrem.net/p2pvsim2/timeline 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] Version 1.28 release?
On Jan 10, 2014, at 13:30 , Michai Ramakers wrote: * End of utf: 2 errors so far ** * Final result: 2 errors out of 18915 tests * Failures: merge-utf-24-23 merge-utf-24-32 The same tests are failing on my machine: $ uname -a Darwin pc6.home 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64 $ ./fossil version This is fossil version 1.28 [1f10199a09] 2014-01-09 21:12:11 UTC 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] Version 1.28 release?
On Jan 10, 2014, at 15:29 , Richard Hipp wrote: Thank you. But those antique test cases don't really matter that much. (The test failures you are seeing are likely due to problems in the tests themselves, not problems in Fossil, though we will verify this prior to release.) Well, an error in a test is still an error to fix. If you want some specific command to run in order to validate Fossil, please try these: fossil all rebuild fossil all test-integrity Let me know if either of these commands gives problems for any of your repositories. Thanks. Both worked perfectly. If I happen onto any real-world error, I will not neglect to cry out loud ;) 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] Version 1.28 release?
On Jan 9, 2014, at 16:00 , Martin S. Weber wrote: But I want Fossil to follow the latest SQLite alphas, not the latest SQLite stables. That's the whole point: Fossil supports SQLite as a test platform. SQLite stable has already been thoroughly vetted and tested and there is little point in testing it further. I want Fossil to run with the latest SQLite on trunk to smoke out bugs early. ...but fossil in itself is a pretty awesome piece of software, that's expected by its users to be stable -- at least for releases. I second this view, Fossil is definitely valuable on its own merit. As such, its stable versions should not contain alpha-quality code from other projects. 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] Version 1.28 release?
On Jan 9, 2014, at 16:14 , Richard Hipp wrote: On Thu, Jan 9, 2014 at 10:12 AM, Remigiusz Modrzejewski l...@maxnet.org.plwrote: I second this view, Fossil is definitely valuable on its own merit. As such, its stable versions should not contain alpha-quality code from other projects. SQLite alphas are more robust that stables of most other software projects. Good point. However, this is one that can be hard to explain to distributors. It would be a shame to see new Fossil releases not adopted due to that. Disclaimer: I have no idea if this would be the case. Personally, knowing SQLite testing, I have nothing against using current version in my system. 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] Version 1.28 release?
On Jan 9, 2014, at 16:35 , sky5w...@gmail.com wrote: Took time to reply, cause I had to clean the coffee I spit up! A released application should be considered stable and a conservative view would say its libs should not contain alphas or betas. The ease of compiling a bleeding edge Fossil.exe is already in place for those wishing to gain the latest features in trunk. You do realize that alpha and beta are just words? With different quality assurance procedures in different projects, trying to use them as a gauge of anything else than releaser intent is misleading. SQLite QA is so impressive that some may be pretty comfortable with having any version, provided it has passed a full test suite, included in their systems. The problem here is the message sent by the word alpha. What it usually means is I just wrote it, hope it will not explode in your face, but no warranties. Therefore if we want to say Fossil is rock-solid, we can't say it uses alpha libs, just to avoid the confusion, no matter the actual quality. 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] Version 1.28 release?
On Jan 9, 2014, at 21:28 , Warren Young wrote: On 1/9/2014 13:17, Richard Hipp wrote: SQLite alphas are more robust that stables of most other software projects. Are you asserting that no data-destroying bugs have ever appeared in a SQLite alpha? Yes, I am. Are you aware of any that I missed? I'll take you at your word. I'm not going to go trawl the SQLite changelog to try and prove you wrong. I'm just uncomfortable being conscripted into someone else's alpha testing program, especially when that test involves my work product, purposely stored in a central location[*] for archival purposes. Exactly my point about message sent by the alpha word. [*] The fact that Fossil is a DVCS doesn't ease my mind on this matter. All that means is that if there ever is a data loss, it will take some time to propagate among the copies, during which time I *may* catch it in time to recover, before the last copy gets tainted. The fact that Fossil is sort of write-only should. By design Fossil does not allow changing (thus destroying) any historical records. The only unwanted thing that can conceivably propagate is your CC number in a test file. If you are concerned by new software errors eating your code, simply don't update your central location. Fossil can easily interoperate in the distance of many versions. 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] Version 1.28 release?
On Jan 9, 2014, at 21:38 , Remigiusz Modrzejewski wrote: [*] The fact that Fossil is a DVCS doesn't ease my mind on this matter. All that means is that if there ever is a data loss, it will take some time to propagate among the copies, during which time I *may* catch it in time to recover, before the last copy gets tainted. The fact that Fossil is sort of write-only should. What I meant is obviously append-only. By design Fossil does not allow changing (thus destroying) any historical records. The only unwanted thing that can conceivably propagate is your CC number in a test file. If you are concerned by new software errors eating your code, simply don't update your central location. Fossil can easily interoperate in the distance of many versions. 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] ChiselApp ChangeOver Complete
On Jan 7, 2014, at 18:51 , Gour wrote: Hmm, in my case I'm considering repo having some of my config files which, among other things, contain my email passwords etc. Why on earth would you give this kind of information in plaintext to any third party? Even when you trust the person, there are so many things that can go wrong in this setup... 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] How to make a private branch public?
On Nov 24, 2013, at 12:41 , Rolf Ade wrote: Andy Bradford amb-fos...@bradfords.org writes: Thus said Rolf Ade on Sat, 23 Nov 2013 21:36:02 +0100: My test repository is a very simple one, only a few test commits. Is this way - delete from private with an sqlite tool on the repository database - really a working way without sideeffects, to make private branches public? Perhaps you could merge the private branch into the non-private branch? Yes, I know that this is possible. But I'm asking for more. I not only want to make the result of my work within the private branch public, I want to disclose the whole history of that work. There is no way to do this right now. Current implementation of private branches is more of a hack. A proper solution would allow push/pull of a specific branch. Which was proposed many times, but never fully implemented. 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] 2-way sync between Git Fossil
On Oct 15, 2013, at 17:34 , Matt Welland wrote: I have done what Ron suggests before and it works well but it is initially complicated to set up. A generic script or tool to do this would be very nice to have available. I created vendor branches, one for each system, the git branch in fossil would track the git master and the fossil branch in git would track fossil. I use rsync to mirror the add/remove/change of files and then script up the commit to capture the comment, time stamp, user etc. of the incoming data. After rsync'ing in the change and committing it the script merges the change to the trunk. It is very complicated but once set up it works great. BTW, I've done this for other systems but never tried it with git. I'm not sure if there are any git related gotchas. One important question: what is wrong with fossil import --git and fossil export --git? 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] http-proxy + https
Hi, I have a completely OT remark: Your certificate has expired a long time ago... 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] Inofficial naming contest...
On Jul 30, 2013, at 12:06 , Stephan Beal wrote: Hi, all, As most of you know, work has begun on a prototype of what i unfortunately dubbed fossil v2. As it turns out, everything i want to do can be done on top of current repos, with no repo-level incompatibilities (so far, at least). That means it's not really v2, but instead provides an alternate interface for v1 repos[1]. That just shows how good is the design :) - libfossil - nothing wrong with that, IMO I'm for this one - just keep things simple. 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] how to delete old history?
On Jul 24, 2013, at 13:36 , Petr Pudlák wrote: I have a several year old project that has been managed in several VCS over its lifetime, and for past year or two it has been managed using Fossil. The history of the project contains some ancient code that is not necessary now, but worse, it also contains some ancient binary library files, which make the history quite large. Is there a way how to abandon some old code, for example to delete every commit that is older than some date? I could export it to GIT, there make the change and import back, but this will change code commit hashes and therefore I'm not sure if it would be possible to keep the relations between tickets, commits and commit messages. Exporting to git was my first idea. If there are just a few of those big binary files, you can use shunning. Otherwise, I guess you'll need to script something using fossil deconstruct, but I have no experience with that route. 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] Random thoughts on Fossil v2
On Jul 21, 2013, at 12:54 , Stephan Beal wrote: To help bootstrap the process of figuring out what Fossil v2 might look like i have started writing down ideas in a public Google Doc: https://docs.google.com/document/d/12g0s5A2TPX7-y47Nsw235rvsjcuh49TnHfMDB4ASvlo/view And why not a public Fossil repo? The answer to this question may give some insight into what's not perfect with Fossil... 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] cygwin distributes fossil
On Apr 4, 2013, at 05:04 , rene wrote: Wow , and 4 or more leading linux distros have fossil as a package ! This puts Fossil in, well, about the top twenty thousand opens source projects? Not that big news. There's also the current version in Homebrew (package manager for Mac), which contains only around 2.5k projects. 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] Chiselapp.com shutting down
On Mar 29, 2013, at 15:34 , Richard Hipp wrote: Yes, I suppose there really ought to be a hosting service for Fossil someplace So I'm exploring the option of setting up a new one. What if we were to extend Fossil itself so that it was capable of hosting multiple projects after the fashion of chiselapp? This was my way to see the future of Fossil some time ago. See the self-register feature, the only one for which my motivation sufficed... I pretty much loved to think of Fossil as Github in a box. But it always was not enough Github in it to be sufficient. I agree that user and repository management is important. As are some quality of life things, like default ticket configuration and markdown support. But what Fossil really lacks for the open source world is the fork/pull request workflow. Without it it will rest confined to the smaller/better organized teams. Thus it will not need a hosting service that much. Just my $0.02. 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] A warning on 'undo'
On Jan 18, 2013, at 17:49 , Lluís Batlle i Rossell wrote: On Fri, Jan 18, 2013 at 11:46:50AM -0500, sky5w...@gmail.com wrote: When in doubt, I run: fossil status Well, I usually don't doubt. If fossil doesn't warn me, I consider it hasn't thrown away any my local changes. And I don't want to doubt. :) That's an opportunity for improvement: automatically stash local changes before destroying. 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] Suggested way to sync to multiple servers?
On Jan 11, 2013, at 00:47 , org.fossil-scm.fossil-us...@io7m.com wrote: My use case here is that I've got repositories hosted on http://fossil.io7m.com but I've also got an exact mirror of that site on my internal network here that's used for testing quickly on multiple machines/VMs (and will now be polled very frequently for CI testing, which would be slow and would start to get expensive in terms of data usage with the number of repositores over the WAN). Mirrors can be easily kept up to date with cron. An empty (no commits exchanged) sync is something like 0.03s for my laptop's CPU, so it can be even every minute without overloading the machine. I'd quite like to either be able to push to multiple remotes, or possibly to be able to push to a remote and then have that remote push to a further remote. Well, with the new Tcl integration there is supposedly a way to do post-sync hooks. Unfortunately I didn't find any time for Fossil in the last few months, so can't help with 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
Re: [fossil-users] Fossil vs. Git/Mercurial/etc.?
On Dec 18, 2012, at 14:42 , Gilles wrote: Out of curiosity, if someone is well-versed with Fossil and the main DVCS systems (Mercurial, Git), I was wondering how Fossil compares to them, for a single user, a small team (up to 20-30), and big teams (thousands). http://en.wikipedia.org/wiki/List_of_revision_control_software#Distributed_model Besides the fact that Fossil includes a wiki and a bug tracker, does it offer features that would make it a better solution than the big names? Maybe I missed it skimming the thread, but I didn't notice anyone telling about the big point. There is an attitude difference between Fossil and the other two, which put in database terms would be: Fossil does replication, Git and Mercurial do sharding. The big names have been created for huge teams, where people generally don't want to be overwhelmed by tentative work done by others. Therefore they work in isolation, issuing pull requests once the thing is done. Especially in Git it's popular to compress all the commits to be pulled into one big commit. But the important thing is the isolation. It stands in stark contrast to Fossil's everybody has a copy of everything. In almost all the projects I've seen this is realized by another thing that you don't see in the big names: developers autocommit to a central repository. This renders Fossil basically a modern reincarnation of Subversion, what is appealing to a lot of people. As a bonus you get, a little dumbed down, installation of (distributed) Trac for free with every repository. 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] Fossil vs. Git/Mercurial/etc.?
On Dec 19, 2012, at 19:56 , Mike Meyer wrote: The big names have been created for huge teams, where people generally don't want to be overwhelmed by tentative work done by others. Therefore they work in isolation, issuing pull requests once the thing is done. Especially in Git it's popular to compress all the commits to be pulled into one big commit. But the important thing is the isolation. This is a description of workflows, not SCM properties. Of course. But bear in mind that the tools are optimized for certain cases that creators had in mind. Fossil was created for a team of (IIRC) three employees of a single company. Git was created for a fuzzy community of some few thousands people. It stands in stark contrast to Fossil's everybody has a copy of everything. Except for private branches. There's been some discussion about adding more control over push/pull to fossil, but I don't believe it's happened yet. Private branches are a pretty recent addition. I believe that the fine grained pushing/pulling will also come sooner or later, once one of folks involved with Fossil feels a need for it. 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] pushing only specific branches to specific servers?
On Dec 12, 2012, at 08:28 , Gour wrote: On Tue, 11 Dec 2012 18:59:59 -0600 C. Thomas Stover c...@thomasstover.com wrote: Is there some way to push just a specific branch to a server other than the private branch feature? No, but it was discussed in the past...btw, I'd also like to have selective push/pull feature. IIRC the conclusion of these discussions always was: there's no problem with that, we just need someone who wants it badly enough to implement it. Funny how this never happened. 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] server SSL support
On Nov 13, 2012, at 15:09 , ST wrote: why not put it inside in order not to bother with 3rd party stuff? To keep the core small? 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] fossil and CI
On Oct 23, 2012, at 13:28 , sphere foura wrote: My question is: Which CI tool best connects with fossil? Can anyone back their assertion with a proven implementation? The last time I checked, there was no integration provided by any of them. But it's usually no problem to provide your own script to do the checkout, what makes the matter pretty trivial if you want periodical tests. I wanted post-commit, but there was no support for that in Fossil at that time. There allegedly is now, through some Tcl hooks, but integrating it with CI seems to be still uncharted territory... Kind regards, Remigiusz Modrzejewski PS. Excuse any grammar mistakes, I'm nearly braindead after too long meeting. ___ 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] comparison with Git
On Oct 9, 2012, at 20:44 , Eric wrote: On Tue, 9 Oct 2012 12:19:59 +0200, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: But who would prevent a cow worker from using them? Cow worker Reference to the Dilbert comics... The idea is that, especially in corporate environments, you'll at some point end up working with people who'll be, in your eyes, highly defective. Unless you're always in exclusive control of hiring, you'd better think of mechanical ways to enforce your vision of the project. Actually... No. Fossil, with it's monolithic single-app design, is relatively hard to both extend and embed. Actually there are two kinds of people in the world, those who expect something to do whatever they think it should, and those who look at what it is designed to do, and how it is designed to be used, and then either use it accordingly or find something else. Of course success in extending or embedding depends on the level of available skill in awk or Perl or Expect or whatever. Remember that the target end-user for Fossil is a developer! Yeah, you pretty nailed it. A perfect explanation why Fossil's integrations into various IDE's, GUI front-ends and other integrations are so popular. I may be OK with CLI, but it already bit me a few times: I can not use Fossil in my day job, because there's no Eclipse plugin (apart from that, the team said whatever, we're free to start new projects in whatever VCS that Eclipse supports). But don't say it's easy to extend by writing a separate client or ipc-ing to this one... Why not, it's a perfectly acceptable technique. Acceptable, yes, in some circumstances. But compare: open3 a process and parse the output (is it even guaranteed to be stable?) to a function call... 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] comparison with Git
On Oct 10, 2012, at 14:28 , Mike Meyer wrote: Well, the lack of an in-binary API certainly isn't the reason there's not an Eclipse plugin. The Eclipse license is incompatible with the GPL, so any scm that's GPL'ed (*cough* git *cough*) isn't linked with Eclipse, but probably uses a process API. But Fossil is not GPL. It would make perfect sense to link it wherever you'd like. For Git, it seems that it's primary implementation is a bit too messy for most big projects, so they simply reimplement it. Eclipse's implementation is called JGit. And it does provide a reasonably stable Java API, used by a few projects. On the other hand, Fossil's implementation is (apart from the regular forking) quite nice. I'd bet you a beer that once the JSON API is finished (in my already outlined understanding), it will be used by some useful projects. 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] comparison with Git
On Oct 9, 2012, at 13:30 , Joe Mistachkin wrote: Remigiusz Modrzejewski wrote: Actually... No. Fossil, with it's monolithic single-app design, is relatively hard to both extend and embed. I strongly disagree with this statement. Fossil is very extensible in the classic Unix sense, by building command lines and parsing the resulting output. We both know how this compares to having an actual API... Also, much work has been done, by myself and others, to make Fossil extensible using Tcl. So, is it finally possible to script pre-/post- commit hooks? Finally, Stephan Beal has done quiet a lot of work to make the JSON API a reality, which enables quite a few useful extensibility scenarios. Yes, but his work would be much easier if it wasn't an afterthought. Plus, this is still a work in progress. Only once it is finished, and by that apart being functional I mean included in the official build and documentation, we can finally say that there is a Fossil API. She has not been ignored. I have been assigned by Richard to help with integrating her work into Fossil and have been in direct contact with her. Also, you may notice the markdown branch in the official repository as of October 3rd, 2012. Oh, I missed that part. That's happy news to me :) 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] comparison with Git
On Oct 9, 2012, at 16:36 , Joe Mistachkin wrote: Remigiusz Modrzejewski wrote: So, is it finally possible to script pre-/post- commit hooks? More or less: http://www.fossil-scm.org/index.html/artifact?ci=trunkfilename=src/xfer.cl n=1201-1205 The key is that these are actually post-transfer scripts. It is up to the called script to determine how many commits, if any, have been done since it was last called. I have a working proof-of-concept Tcl script on a private repository that does this and sends mail via SMTP if a commit is detected. The real expressive power here comes from having Tcl enabled at compile-time (and via the runtime setting) and being able to seamlessly invoke it from TH1. That's nice. I guess I'll try to use it in the following months (for continuous integration). But it's still impossible to obtain policing with that. Like, refusing to receive a push if some commit was not properly signed. This would be a pretty useful thing that's long time possible in the competing products. Thankfully I will not need that for a long time and hope Fossil gets it before 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
Re: [fossil-users] Agile Fossil?
On Oct 9, 2012, at 17:43 , Dirk Reiners wrote: I've just started using Fossil, and I was curious to see what the intended development directions were. Specifically I would be interested to know if there were any plans to add some agile support to it. I'm not really expecting anything fancy, primarily better support for milestones beyond the existing Events (which I see more as milestones after the fact), so tickets can be associated with milestones and maybe some burndown chart. Something along the lines of what Veracity supports (see http://www.ericsink.com/entries/burndown.html), but not necessarily as colorful or fancy. Is there any interest in that? Is anybody working on something like that? Is that outside the scope of fossil and will never be integrated? Fossil's ticketing system is more general (and more DIY) than most of what you find. It's perfectly possible to add a milestone property to the ticket and then create a report grouping them together. You can add nice progress bars in js by editing the template. Therefore, it's a matter of you setting it up. Or someone doing it and sharing afterwards (there is already a mechanism in place to import/export things like that). If you feel up to the task, see the /tktsetup of your repo. 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] query list of files from fossil within /www/ embedded website
On Sep 3, 2012, at 10:56 , Carlo Miron wrote: On Mon, Sep 3, 2012 at 8:06 AM, Jan janus...@gmx.net wrote: Background: I am /misusing/ fossil as a JSON database. Are you aware of UnQL unql.sqlite.org/? Does this thing have some nicer documentation somewhere? Seems intriguing, but there's nothing that would reveal if it's real nice with just a quick glance. 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] The future of markdown-in-fossil
On Aug 3, 2012, at 11:53 , Michal Suchanek wrote: On 3 August 2012 11:23, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: +1 Why markdown and not one of the dozens of other wiki syntaxes? Because markdown is a very popular one, used by github, and we have on board the creator of a major implementation (the one used by github, iirc). I don't find wiki syntaxes really easy. Maybe a bit easier to type than HTML but definitely not easy to read or remember, especially since there are dozens of slightly (and not so slightly) different variants. That's why half of the web seems to standarize on markdown. The same web that was mostly writing HTML a few years ago. Note there are JavaScript hacks for interpreting random wiki syntax so you can have markdown interpreted without any direct support in fossil. Note there are good wiki engines out there, so no need for one in Fossil too. But once we set the scope to include something, please don't keep it half-hearted... 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] The future of markdown-in-fossil
On Aug 3, 2012, at 12:19 , Michal Suchanek wrote: Why markdown and not one of the dozens of other wiki syntaxes? Because markdown is a very popular one, used by github, and we have on board the creator of a major implementation (the one used by github, iirc). Github has a cute logo but I would not turn to it when looking for sound technical solutions. Still, somehow, they don't seem a failure. A cute logo can't buy that... That's why half of the web seems to standarize on markdown. The same web that was mostly writing HTML a few years ago. Does not seem that way to me. I deal with sites using various wiki format variations. If you want to make your point on that then supply more data, please. No data. Just the anecdotal: a few years ago most input fields I've hit on the web accepted sanitized HTML, now they take markdown. Yeah, they're usually not wikis (but the wiki engine I use actually uses markdown). Note there are JavaScript hacks for interpreting random wiki syntax so you can have markdown interpreted without any direct support in fossil. Note there are good wiki engines out there, so no need for one in Fossil too. But once we set the scope to include something, please don't keep it half-hearted... And it has been said that markdown is out of the scope of Fossil. I am not to decide that but I have to agree. Once you let in markdown people used to some other wiki syntax would argue they have needlessly hard time and there would be no end to the stream of requests to include yet another. I've read the we'll have requests for all the markups in the world argument many times. I can't remember anyone actually coming and asking for *anything* else than markdown. 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] Fossil on Android or compiling with tcc?
On Jun 20, 2012, at 13:07 , Kostas Karanikolas wrote: I'm running an Arch linux chroot on my tablet. Compiling fossil from source on the tablet worked fine for me. No patching necessary. Well, your Arch Linux chroot has a complete Linux useprspace, doesn't it? I don't know if it's the case for typical Android... 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] Anonimous can't create tickets on fossil-scm.org?
On Jun 19, 2012, at 11:17 , Александр Орефков wrote: subj. Earler I can create tickets on fossil-scm.org, but now I can not. I found some errors in sources, wheare I can pos it? Here, to the list. The ticket system at http://fossil-scm.org was swamped by testing tickets and had to be turned off. 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] [OT] Anonimous can't create tickets on fossil-scm.org?
On Jun 19, 2012, at 16:26 , Richard Hipp wrote: If people show up and are interested, we can work on this at the Fossil code sprint in Munich, two weeks from today. BTW: any chances for a sprint in the French Riviera in any foreseeable future? ;) 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] Adding settings
On Jun 11, 2012, at 09:03 , Baruch Burstein wrote: Is there an easy way to add settings (preferably on a per-repository base) to the `fossil settings` command? And if so, is there an easy way to also add them to the web interface? I once added the *self-register* thing after just a few minutes of looking around the sources. So yes, I'd say it's easy. At least if you have *grep* in your system ;) 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] New CSS on the Fossil homepage
On Mar 31, 2012, at 18:31 , Richard Hipp wrote: So now I have three variants up for consideration: (1) http://www.fossil-scm.org/ (2) http://www2.fossil-scm.org/ (3) http://www3.fossil-scm.org/ #1 is the recent change, with the rock background, which I (being very old school) prefer. #2 is the original before recent changes. #3 is like #1 but without the background image. I dislike the disturbing margins. Apart from them, the change seems ok. 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] Make a CGI request WITHOUT a script file
On Mar 4, 2012, at 10:43 , Guillermo Estrada wrote: As far as I know the proxy server way can't serve multiple repos, that truly would be the most optimal way to host such a service (agan, disk latency) starting with pretty small hardware. But then again, not having to rely on lots of cgi scripts to serve the repositories it's a nice start to efficient hosting. Why? The server itself supports multiple repositories. I'm reverse-proxying to a single Fossil instance serving over 20 repos at http://dev.lrem.net/ and it works like a charm... 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] how to maintain a set of patches?
On Feb 26, 2012, at 15:00 , Leo Razoumov wrote: On Sun, Feb 26, 2012 at 04:48, Stephan Beal sgb...@googlemail.com wrote: On Sat, Feb 25, 2012 at 9:48 PM, Leo Razoumov slonik...@gmail.com wrote: I sincerely hope that fossil was not designed with only one work-flow (SQLite and fossil) in mind. Am I mistaken? If i'm not sorely mistaken, fossil was indeed originally designed for exactly one purpose: managing the sqlite repo. GIT was originally designed as a BitKeeper replacement for linux kernel. Then the scope broadens... Well, IIRC Mercurial was even more narrow, originally created to keep only some subsystem of the kernel ;) 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] _FOSSIL_ file grows large
On Feb 8, 2012, at 17:05 , Richard Hipp wrote: I generally don't stress over a 10MB file on my 1TB disk drive, though... Still, it probably would not hurt to have Fossil do vacuum from time to time, would it? 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] zip/tar patch
On Feb 7, 2012, at 23:11 , Stephan Beal wrote: Agreed completely - spaces in filenames are evil. (let the flame wars begin ;) Well, shouldn't a good filename start with - anyways? ;) 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] Derived code, not to be pushed public
On Feb 5, 2012, at 20:47 , Lluís Batlle i Rossell wrote: But I suspect that there are people using fossil and having a reasonable workflow for those cases. I wonder what they use. A lot of care to only pull towards the derivatives? 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] documentation clarification
On Feb 1, 2012, at 15:18 , Chris Peachment wrote: I can't speak for MS-Windows or MacOS but Ubuntu Linux uses NTP by default. So does OS X. 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] Should distributed binary require libnss to connect over http?
Hi, I've hit a surprising obstacle. I've tried to use Fossil, the binary from the website, on a heavily stripped down Linux system. But trying to clone end with: fl: can't resolve host name: dev.lrem.net I traced the problem to be lack of libnss_dns.so.2. But as far as I understand, this library is needed only for https, isn't it? This failed while trying to use plain http. Is this expected? Pozdrawiam, 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] Should distributed binary require libnss to connect over http?
On Jan 29, 2012, at 20:36 , Remigiusz Modrzejewski wrote: I've hit a surprising obstacle. I've tried to use Fossil, the binary from the website, on a heavily stripped down Linux system. But trying to clone end with: fl: can't resolve host name: dev.lrem.net I traced the problem to be lack of libnss_dns.so.2. Nah, should read more carefully. The trace actually reads like this: open(/lib/libnss_dns.so.2, O_RDONLY) = 8 read(8, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0\0\20\0\0\0\0\0\0..., 512) = 512 close(8)= 0 open(/usr/lib/libnss_dns.so.2, O_RDONLY) = -1 ENOENT (No such file or directory) munmap(0xf7746000, 8285)= 0 write(2, \rfl: can't resolve host name: de..., 43) = 43 No other indication what's wrong in strace. For ltrace, I get: ltrace: Couldn't find .dynsym or .dynstr in /usr/bin/fossil But I'm already getting too lazy to continue, sunday evening projects are meant to be pure fun ;) I'll pick up from here later this week. 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] What you think about this functionality?
On Jan 26, 2012, at 20:38 , Lluís Batlle i Rossell wrote: On Thu, Jan 26, 2012 at 08:36:46PM +0100, Remigiusz Modrzejewski wrote: I've stumbled upon a description of something, that I missed once or twice in Fossil: http://nuclearsquid.com/writings/git-add/ Nothing that great: an ability to commit only part of changes to a file. This kind of a thing can as well be scripted out, or implemented with use of an external merge program (I acutally manually set up to use vimdiff the few times I needed it). Any opinions? I find that git work style of git add/commit (the head, the index, the working directory) very annoying. I'm quite happy fossil does not work that way. :) But this is *not* about the index. It's about finer granularity of committing. 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] What you think about this functionality?
On Jan 26, 2012, at 21:06 , Richard Hipp wrote: The --interactive option is not really appropriate for the commit command, for the reason cited above. But I can see an --interactive option being useful for the stash apply command, so that you could selectively pull parts of a stash into your working copy. I can also see it being useful on merge, especially when combined with --cherrypick. But not on commit; the thought of adding --interactive to commit gives me shivers. While I see nothing bad with partial commit (well, if partial commit is bad, why can we do it at file level?), doing it at stash does the trick and feels a bit more elegant. I'd vote for this option. Pozdrawiam, 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] Supporting markwon syntax for wiki
On Jan 13, 2012, at 12:49 , Jeremy Cowgar wrote: Fantastic. Hopefully this makes it into the trunk version of Fossil. Yeah, shortly after discount author signs the copyright leaflet... 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] Supporting markwon syntax for wiki
On Jan 13, 2012, at 13:36 , Bill Burdick wrote: It's BSD licensed -- does he still need to do that? I don't have the time to read through the verbiage again, but IIRC yes. Any submission to Fossil has to go with full assignment of copyright, which has to be done by the original author. This way it was possible to make the move from GPL to BSD... But some code from the early days, when no contracts were signed, had to be dropped. 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] fossil for photos archive?
On Jan 11, 2012, at 16:09 , Thomas Stover wrote: Just about every time I get started on a new software tool, I revisit the question of it will help me finally get my family photos under control, regardless of whether or not it makes any sense. Storing large numbers of pictures in subversion for instance, turned out to be a very bad idea. Anyone else doing this? I'd say this is not a good idea. While it can work, what you usually want to do with a photo collection is far away from what you want to do with a bunch of source code files. There is little benefit of Fossil compared to any other synchronization tool (I'd go with rsync, most people like dropbox). On the negative, you'll end up with a huge repository file and no convenient way to delete photos. 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] fossil for photos archive?
Oh well. Just trying to find more ways to be lazy. rsync etc still don't give you a way to share the pictures on a website. Well, I'd rsync it to some public_html... Thumbs and indexes are easy to do with a cron job, or a custom index.php or whatever. Seems to be a lot less work than scripting Fossil to do it well. 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] Authentication via URL
On Nov 22, 2011, at 9:32 PM, Jeremy Cowgar wrote: So we are back to square one on accessing an RSS feed that is protected via a normal RSS reader. There may only be two solutions to this problem: 1. Use allow authuser=johndoeauthpass=secret as a URL parameter 2. Forget accessing secured RSS feeds Any other ideas? Try a smarter RSS reader? I remember having Opera read a few protected feeds... 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] Authentication via URL
On Nov 22, 2011, at 9:46 PM, Jeremy Cowgar wrote: Try a smarter RSS reader? I remember having Opera read a few protected feeds... It's not that simple. Most RSS readers will authenticate via Basic Authentication, which most feeds are setup as. Fossil, on the other hand, does not directly support Basic Authentication. In order for you to read a protected Fossil RSS feed you have to login via the Fossil login screen. No RSS reader (that I know of) will do this. Well, I've mentioned one already: Opera. I've never seen a http basic auth protected feed. The ones I've mentioned were forums where you had to login using customizable by templates login pages. I had to log in at that page and set feed syncing to an interval smaller than session expire time. Worked flawlessly. It would have to be told where the login screen is, what the input names are for the username and password fields, then how to interpret the results. I'm pretty sure that should not be a problem. This procedure can be replicated in something like 5 lines of Python. Compared to what I believe is the codebase of a typical rss reader, this does not look too bad... 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] limited ticketing
On Nov 18, 2011, at 3:41 AM, Tomek Kott wrote: If we have granular permissions for tickets, then we should probably also have it for the wiki (view attachments, view history), we should also separate attach and delete for wiki and tickets, and maybe even throw in permissions related to the timeline and files (such as view newest view hitsory, view patch, view diff) and maybe even download zip instead of tar file. Don't forget about tags and even open and closed names. You could EVEN create permissions for each artifact! That would just be easier, because you wouldn't need to worry about the type. OR We could realize that to do this properly would require a good CMS, which fossil is not, and keep it simple. You know that by similar funny implications we can prove that most of Fossil is actually redundant... Actually, why do we even have a permission system, if Fossil is an internal development tool? 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] limited ticketing
On Nov 17, 2011, at 11:01 AM, ST wrote: is it possible to configure fossil server so, that some clients will be able only submit tickets (and even not see other tickets or maybe see only tickets that they have submitted)? This mode would be useful for customers whom you want to submit bug reports without being able to observe the whole development process. Have you looked into permissions page in the admin section of the web interface? IIRC this is perfectly possible. 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] limited ticketing
On Nov 17, 2011, at 6:28 PM, Stephan Beal wrote: On Thu, Nov 17, 2011 at 6:02 PM, ST smn...@gmail.com wrote: as far as I understand one can enable/disable ticket viewing completely, but I don't see a way for a user to be able to see/comment/append _only_ to tickets submitted by him... Fossil doesn't offer that level of granularity. But it should have, as this seems to be a really reasonable (and perfectly doable) thing to have. Thus I open a ticket (sorry, not time to donate for it): https://fossil-scm.org/index.html/tktview/620506c3b211ff839d11230a6e2a31128de94bf4 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] Providing fossil as a vcs, wiki or blog for 'users'
On Nov 13, 2011, at 10:33 PM, Julian Fagir wrote: For people who dislike fossil as a wiki or vcs, there are still other solutions, but they're not automated, so that wouldn't stop me. So, my question: Do you think fossil is appropriate? As a vcs yes. The ticketing system needs some setup to fit my taste, but that's not hard. But, sadly, the wiki is way too simplistic to be practical. But this probably will be resolved one day. As I said, I'm relatively new to fossil, and may not have tried out all features. Would you have security concerns about that? Nope, Fossil is not dangerous to the machine it runs on. You can put it into chroot to feel extra safe in case of security breach. And do you have any suggestions what might help me with that? Are there standard settings you would suggest? Look into WAL mode for the database. 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] Providing fossil as a vcs, wiki or blog for 'users'
On Nov 16, 2011, at 4:11 PM, Stephan Beal wrote: As a vcs yes. The ticketing system needs some setup to fit my taste, but that's not hard. But, sadly, the wiki is way too simplistic to be practical. But this probably will be resolved one day. Actually the JSON API is far enough along that a completely custom wiki could be based on it, using one's own custom wiki syntax, provided a client-side renderer is available for it. The user management and wiki APIs are feature-complete enough to support this, and implementing a proof-of-concept for this is on my (long) list of TODOs for the JSON API. The only (IMO) significantly missing feature in this area is the ability to get historical versions of the wiki pages - currently we only serve the latest version in the JSON API (fixing that is of course also on the TODO list). Actually, I'm not sure if that's that good idea. This way you can bring client incompatibility, unless you mean writing in a better markup, but saving (and loading from) the plain Fossil thingy. It surely can be done, just is not as trivial as we'd like it to be. 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] [best practice] Including external dependencies
On Nov 14, 2011, at 3:19 PM, Jacek Cała wrote: A best practice question: What is the preferred way to include external libraries in a fossil repository? I mean larger dependencies like boost. For small libs and tools like a few binary or source code files, I tend to include them directly in the repo but for larger ones it doesn't seem like a proper approach, esp. when the library code is much larger than my sources. Depends on the environment, but I'm kind of a fan of it's scripted approach. I remember a friend putting into our cmake some black magic that would downloadbuildinstall missing dependencies. I guess if your shop is homogenous this should not be that hard. 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] Fossil and Jenkins?
On Nov 7, 2011, at 7:14 PM, Nolan Darilek wrote: Just wondering if anyone has gotten Fossil to work with either Jenkins or Hudson for CI? My understanding is that these systems support a periodic poll mode that can compensate for the lack of hooks. I'm about to start using Fossil more heavily in team projects, and in situations where I may wish to deploy via push. So I'm wondering if anyone has gotten this working with Jenkins, or indeed with any other CI. If there's a better fit for Fossil then I'd love to know about it. I've seen some BuildBot howto somewhere. It worked fine IIRC. 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] Fossil is Awesome
On Oct 26, 2011, at 11:50 PM, Stephan Beal wrote: The topic of real hooks has come up many times, and the main reason it hasn't been added so far is platform portability. (Sorry, i don't mean to start another dead-horse-beating thread.) Nope, this has already been resolved. The reason now is there is not enough programmer throughput in the project. Or however it was worded. 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] Fwd: suggestion on fossil
On Oct 19, 2011, at 2:18 PM, Richard Hipp wrote: I have two suggestion on fossil: (1) support LDAP. It is a essential function for a large enterprise to manage users login and authentication. (2) support lock command, http://veracity-scm.org has this command. My $0.02: both seem to be pretty valid points... ___ 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] Veracity (was: Fwd: suggestion on fossil)
On Oct 19, 2011, at 2:50 PM, Stephan Beal wrote: 2011/10/19 Lluís Batlle i Rossell virik...@gmail.com Whether to support locks... I think it can help some users, but I don't have use cases in my day to day. My 0.02€: in some 16 years of using source control, i have never once had a use for (and sometimes been hindered by) locks. IMO anyone who _thinks_ they need them is still living in the 1980's or early 1990's. I seem to be still in the 80's... So how do you cope with edit conflicts on binary files today? And yes, this actually happened to me, one of us applied some pretty gradients to icons, while the other changed their shape... 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] delete a branch
On Oct 1, 2011, at 3:19 PM, Paul Ruizendaal wrote: Perhaps it is bloat, but would it be useful if branches with the tag 'mistake' or perhaps 'hidden' were not shown on the default timeline in the web interface, and having an option for showing the full timeline? It would be a bit like the full file view and the current file view when showing files. I second this idea. Hiding mistakes by default is at least reasonable. 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] minor milestone: Java client
On Oct 4, 2011, at 12:27 AM, Paul Ruizendaal wrote: On 2 Oct 2011, at 11:58 , Joerg Sonnenberger wrote: On Sat, Oct 01, 2011 at 11:22:28PM +0200, Paul Ruizendaal wrote: Doing fork/exec sounds expensive, but on a posix box there is not much difference between that and spawning a thread: http://bulk.fefe.de/scalable-networking.pdf Please don't base decisions on questionable micro-benchmarks. fork+exec is significantly more expensive than thread creation in a multi-processor environment. [...] In any case, the cost of fork/exec would be less than 0.1 ms. As most Fossil commands take much longer than that, I think the proposal is a practical design for wrapping Fossil. Anyhow Fossil is doing only fork, which is pretty cheap. And, unless some crazy security folk take over, there is no reason to change this :) 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] Why the certificate on fossil-scm.org is invalid?
Hi, I'm wondering: why does fossil-scm.org use invalid certificate? This is pretty bad in times when valid certificates are given for free [1]. Is there some technical problem with that? I guess that not having to think if someone is sniffing my password, every time I'm out of home, may be worth the hassle... [1] - http://www.startssl.com/?app=33 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] Why the certificate on fossil-scm.org is invalid?
On Sep 26, 2011, at 11:39 PM, Joshua Paine wrote: having to think if someone is sniffing my password, every time I'm out of home If you're using machines you don't control, I'd say it's much more likely that there's something nefarious logging activity on the machine than listening on the wire. (Of course, it seems governments *do* spend a fair bit of effort listening on the wires, but they're not likely to be interested in your fossil password. Make sure it's not more valuable than it needs to be by not using the same password for more than one thing!) Actually I'm sometimes using machines that I do control in a way, but never really setup - usually by means of live cd. On the other hand I'm working in an environment where we have people actively doing network security research. I think their ethics can be trusted, but still feel a bit uncomfortable every time I see a certificate warning. 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] How to set up a server under nginx ?
On Sep 25, 2011, at 10:38 AM, Lluís Batlle i Rossell wrote:
On Sun, Sep 25, 2011 at 04:33:44PM +0800, i wrote:
I don't want to use CGI, as it's already nginx running . so now I want to
use nginx to set up the server for fossil and I don't know what to do.
Thanks.
What makes you think, that you don't want CGI? I'd say you want CGI, as long
as
nginx is a web server.
Well, CGI in httpd/inetd is going to run Fossil for every request. In the
meantime, Fossil in server mode does a fork for every request too, but it *does
not do exec*. So it can be more performant to just proxy to a `fl server`
instance. Plus, this way you don't have to make your repositories readable by
httpd process.
To answer the original question:
You start your fossil server on a given port, preferably by means of cron.
Then, in your vhost configuration you just put:
location @fossil {
proxy_pass http://localhost:MY_CHOSEN_PORT;
}
And anchor it appropriately. That simple.
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] lol: funny favicon behaviour in local server mode...
On Sep 15, 2011, at 1:44 PM, Stephan Beal wrote: Last night i ran a media player (VLC) web service on localhost:8080. Today when i started 'fossil ui' my browser had cached the favicon.ico from the media player and now shows the VLC favicon in place of fossil's. (Not a fossil bug, by the way.) Still, it can be fixed by fossil providing a favicon ;) 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] Fossil tutorial - Oct 25 in Manassas VA
On Sep 14, 2011, at 6:28 PM, Stephan Beal wrote: Fair enough. Could we convince you to accidentally leave your webcam turned on during the presentation (and conveniently point it as the screen)? ;) Isn't it easier and more responsible to just record a rehearsal? 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] Presentation slides for Fossil?
On Sep 12, 2011, at 3:48 PM, Martin S. Weber wrote: It wrongly claims that fossil is GPL. Rightly - at the time it was given... Fossil got relicensed some time ago. IIRC some code needed to be dropped due to that. See: http://fossil-scm.org/index.html/timeline?r=clear-title 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] Draft doc for JSON/REST Fossil interface
On Sep 9, 2011, at 7:35 PM, Stephan Beal wrote: On Fri, Sep 9, 2011 at 7:04 PM, Twylite twyl...@crypt.co.za wrote: e.g. /timeline produces HTML by default, but /timeline.json would return the same information in JSON. i like that idea. i hadn't thought of simply using an extension. i don't have a strong opinion as to whether, e.g. /json/stat or /stat.json is better. Anyone want to give me their own strong opinion? (We could probably support both - they're stored as string-to-function mappings, but the current path/arg-handling code would need to be slightly different for each case.) My strong opinion: whatever.json is better than json/whatever. It's a matter of semantics, if we want to render whatever in some representation, or we want a representation containing a whatever... I'd say the former. 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] Current status on hooks?
Hi, I'd like to know where we are in the topic of hooks. Their lack is one of the major setbacks of using Fossil. The last time I've noticed a discussion on their topic it was said, that it's blocked by inability to start background processes on Windows. Now there is a way to run Fossil itself in background on Windows. Has this helped towards getting hooks into main line? 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] Current status on hooks?
On Sep 10, 2011, at 7:53 PM, Richard Hipp wrote: (3) Use the FTS4 full-text search engine of SQLite to implement full-text search over the entire repository history. Ha, that was the next thing I was going to ask ;) But unfortunately I'm unable to contribute any programming time this month :( 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] CR/NL warning in .pdf
On Sep 6, 2011, at 1:18 AM, Konstantin Khomoutov wrote: The problem is while PDF is considered to be a binary file (and it indeed usually contains compressed regions, it does contain ASCII header and footer (I think it's its PostScript heritage), so it can be considered to be a plain ASCII file by any tool which does not look for its special magic character sequence (in the first line of the header). Probably Fossil does not do that. That's a bit funny, because the pdf files contain a single \r\n ending not within a compressed region. Converting that to \n doesn't seem to break anything, but did I just kill a kitten? And the more important question: should we make fossil to treat all pdf files to be binary? 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] CR/NL warning in .pdf
Hi, I'm wondering if this warning is OK: ./storage/exp-queue6deads-rectime-N200-s8-r3-b1000-c1_2-upbw28-mtbf1440.pdf contains CR/NL line endings; commit anyhow (yes/no/all)? While committing in a recent trunk build. I just don't know what's the story behind line endings in PDF. 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] Is it possible to edit a ticket's submission time?
On Sep 2, 2011, at 10:40 PM, Stephan Beal wrote: On Fri, Sep 2, 2011 at 9:48 PM, Matt Welland estifo...@gmail.com wrote: # Set your system date to the date for the ticket sudo date -s 08/11/2011 Beware with that - it can confuse your build system. And summon Hastur. Never do such a thing three times in a row. Plus, if you really feel that hackish, just do your business in SQL. 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] Ticket [1b5f29ce63]: Ticket view does not escape HTML
Hi, I'm just pointing towards a ticket that I don't want to fix right now. Maybe someone reading the list but not timeline has some spare time ;) Link: http://fossil-scm.org/index.html/tktview?name=1b5f29ce63 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] SSL support on Windows
On Sep 3, 2011, at 4:32 AM, Liu Chang wrote: Do we already have the pre-built binary for Windows + SSL? Nope, pre-built libraries on the site are complete barebones. I'm on the edge of deciding to provide rich builds for all the systems I use, but Windows is not one of them. 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] fossil performance testing and is it possible to increase the sqlite3 timeout?
On Sep 3, 2011, at 5:15 PM, Dmitry Chestnykh wrote: So now, why wal is not the default? I'm having a trunk build from few days back and a freshly created repo is in delete mode… See disadvantages here: http://www.sqlite.org/draft/wal.html The biggest one is that it requires two additional files. Ok, but then I'd say it should be documented somewhere. For now the closest thing to documentation of this aspect (which is quite important, as seen in this thread) is mention of existence in the help of fossil rebuild. Not enough... 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] Diff after move
On Sep 1, 2011, at 5:14 PM, Stephan Beal wrote: 2011/9/1 Jacek Cała jacek.c...@gmail.com fossil.exe: file XXX does not exist in checkin: You also need to do the mv yourself. fossil mv records the intention but does not actually perform the mv on the filesystem. Which, for me, seems to be quite weird... 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] Spam marks on this list e-mail messages
On Aug 26, 2011, at 4:51 PM, Konstantin Khomoutov wrote: That 67.18.92.124 address resolves to sqlite.org, so I wonder if it's possible to somehow contact spamhaus.org admins for this address to be removed--it seems unlikely that this domain was used to send spam. It is not only possible, but encouraged and well explained here: http://www.spamhaus.org/xbl/ 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] Fossil at Freshmeat
Hi, I took the liberty to submit Fossil to Freshmeat. The URL is: http://freshmeat.net/projects/fossil Anyone with a Freshmeat account is welcome to rate or write a comment. While all my published projects are nearly oneliners, I've had a pretty nice experience with Freshmeat. It seems that a lot of people use it to search for software for Linux. Furthermore, a few sites aggregate entries from it, further spreading the hype. Anyhow, I hope that this brings a nonzero number of users ;) I'll submit every new numbered release to it. If I go missing for whatever reason, don't worry, I gave access to the entry to drh. 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] Wiki formatting with empty lines
On Aug 18, 2011, at 6:44 PM, Jos Groot Lipman wrote: Minor Wiki-problem: paragraphs are create automatically for empty lines. However with the following text it leads to unexpected termination of the first p marker and the last line of text is left-aligned. When you remove the empty line it works as expected. p align=right Next line is empty Previous line is empty /p It is not expected. Wiki help explicitly specifies that paragraphs are delimited using empty lines. Or is this a case of: 'it is a simple wike, play by its rules'? Well, it's a simple wiki... 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] Maybe a bug in sync
On Aug 17, 2011, at 09:09 , Eric wrote: That is another DVCS - Veracity(http://veracity-scm.com). But then you say that there's this other DVCS with a different design philosophy and a different internal structure Don't know about internals, but on the first look the design seems to be pretty similar... And extremally immature as of now: Veracity's current bug tracker really isn't designed for the needs of an open source project. We'll fix that eventually. Anyhow, it looks to me like Fossil plus Scrum support and file locks. Out of which only the second seems to be worth it in some corner cases. See here for explanation: http://veracity-scm.com/qa/questions/102/why-would-you-design-a-dvcs-in-2011-that-supports-file-locks-dvcs-are-meant-to-make-it-needless-to-worry-about-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
Re: [fossil-users] Maybe a bug in sync
On Aug 17, 2011, at 19:14 , Tomek Kott wrote: All info about veracity aside...anyone have any idea why there doesn't seem to be an obvious error in the fossil sync, yet a file is not being synced? The httptrace doesn't indicate anything wrong (to my untrained eyes), but obviously doesn't include file content. Any ideas? Was anybody able to reproduce the problematic situation? I'm not even able to run .bat files, as I don't have a Windows instance handy... 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] self-register
On Aug 13, 2011, at 23:07 , Taylor Everding wrote: I found reference to a 'self-register' setting at http://www.sqlite.org/debug1/help/setting, however after downloading the latest version from http://www.fossil-scm.org/download.html, and `fossil help setting` I could not find it. Is this a new feature, a different branch, or something else. H... Here I see: ~ $ fossil settings | grep self self-register ~ $ DRH has accepted it at the beginning of the year and it has never been removed from trunk. So I'm pretty sure, that you simply have a very old version (pre-1.0). 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] _FOSSIL_ vs. .fos Was: New features for merging
On Aug 13, 2011, at 00:42 , Richard Hipp wrote: Most notably shell's glob ignores dotfiles, what makes them mostly a non-issue for me... And I find the _FOSSIL_ string particularly disturbing on listings. You know you can rename _FOSSIL_ as .fos, right? mv _FOSSIL_ .fos Should I make .fos the default? I'd go with .fossil as default on Unix (there is really no good reason to limit ourselves to 3 letters here) and hidden _FOSSIL_ on Windows. 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] New features for merging
On Aug 12, 2011, at 12:47 , Ben Summers wrote: I've added: * Versionable settings * SSL improvements * Relative pathname listings * empty-dirs setting I'm for the merge in general. I'd argue that relative pathnames could be turned on by default. It's quite hard to imagine anything breaking because of that... Pozdrawiam, 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] New features for merging
On Aug 12, 2011, at 22:28 , Ben Summers wrote: If it has to be in the file system, I'd prefer one file to many. At the very least, change the name of the directory to something that starts with __FOSSIL__ to make it easier to tweak commands to deal with the names. More tools hide names beginning with a dot than they do _FOSSIL_. Most notably shell's glob ignores dotfiles, what makes them mostly a non-issue for me... And I find the _FOSSIL_ string particularly disturbing on listings. 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 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] [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 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] Fossil destroys repositories?
On Jul 27, 2011, at 15:22 , Stephen De Gabrielle wrote: Is revert like 'shun' in that it permanently removes artifacts from the repository? It works on local copy, not the repository. So it deals with on-disk files, not artifacts. 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] Anonymous no longer allowed to create new tickets
On Jul 27, 2011, at 22:06 , Richard Hipp wrote: To report bugs or ask for enhancements in Fossil, please post to this mailing list. Because of noise and test tickets (which by the nature of fossil are permanent) the ability for anonymous users to create new tickets has been disabled. If you have an issue, report it here, and one of the many users with logins will write a new ticket for you, if that is an appropriate thing to do. Good. We should also do something with the noise already in the system. I can contribute a modest amount of time to that end. We have previously implemented a similar policy at SQLite and that seems to be working well. There really needs to be a filter on ticket creation to weed out the (considerable) noise. Perhaps we can figure out a design change in Fossil that makes tickets anonymously-created ephemeral until approved by a registered user Better. But I'm still unhappy with the concept of anonymous participation per se (up to the point that I contributed self-register, which unfortunately is largely ignored). 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] Automatic branch color selection. Was: Question on short-lived branches in fossil
On Jul 23, 2011, at 01:25 , Richard Hipp wrote: An experimental change to implement this is on the server. Add the brbg query parameter to the timeline method to have the background color set by branch name. Add ubg to have the background color set by user name. Examples: http://www.fossil-scm.org/fossil/timeline?n=200y=cibrbg http://www.fossil-scm.org/fossil/timeline?n=200y=ciubg Just what I asked for :) 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] Fossil destroys repositories?
On Jul 26, 2011, at 09:07 , Mike Meyer wrote: And [Fossil] is reported to destroy repositories if someone branches: http://sheddingbikes.com/posts/1306005291.html Any comments? Already discussed at length on the list (http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg04665.html). IIRC, there was a subtle bug that caused a fossil update to update to an empty branch - which then removed most of his files (bug fixed during this discussion). At this point, none of his work was lost. However, he then panicked (not unreasonable) and in trying to get things fixed managed to do things that did lose work. I don't think enough information was ever posted to decide if fossil actually lost work, or if he just managed to destroy it while trying to recover from the checkout of nothing. IIRC he lost his changes by issuing fossil revert, what was the expected result. About general reliability: I've never encountered any data loss/corruption with Fossil. This is even when I use my own compiled versions derived from the trunk at random moments. It's also quite rare to read about any bugs in the software. I'd say it's built to a pretty good quality, but not yet the one of sqlite. Also the process is a bit lacking, with the ticket system being a ghost town (see http://fossil-scm.org/index.html/rptview?rn=2). But then again, it just works :) 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
