Re: [fossil-users] fossil ui not working with recent chrome browser
Am 14.03.2015 um 16:30 schrieb Richard Hipp: On 3/14/15, a...@gmx-topmail.de a...@gmx-topmail.de wrote: I am having problems to access my local fossil repositories with a recent versions of chrome, it looks like only part of the html code is served by the standalone webserver. My question is whether this is a known problem and others can verify it with a similar setup. It is not a problem known to me. Can you try it with version 1.32 and let me know if it is still an issue? yes, I just did that (Fossil version [6c40678e91] 2015-03-14 13:20:34) and still see the same problem: only part of the html-code is rendered and when I look at the page source that chrome claims to have received that is also incomplete. I have now made some more experiments and found that I have the same problems with internet explorer and opera as well, but with firefox I don't have it. As I saw this right after a chrome update I was mislead to believe it was because of that, but probably it is something completely unrelated to that. Of course that makes me wondering even more whether anyone else has ever seen such behavior... Albert ___ 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] Google code shutting down
On 3/14/15, Ron W ronw.m...@gmail.com wrote: Yes, that and making sure the P card in wiki artifacts has the correct parent in it. (Last time I checked, the Edit Wiki Page page did not have a (hidden) field to identify the parent artifact.) I think that works. See, for example, the wiki edit at https://www.fossil-scm.org/fossil/artifact/527bc296a0ef0a29 - the P card points back to https://www.fossil-scm.org/fossil/artifact/0344248b9 which in turn points to https://www.fossil-scm.org/fossil/artifact/bd34092a2f and so forth. But you are correct that Fossil does not currently do anything with this history, other than record 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] New skin: Blitz
Am 14.03.2015 um 16:52 schrieb jungle Boogie: Does anyone else have issues reading diffs? Me too. After years spent glaring at computer screens Ctrl++ became my friend -- being too obstinate to wear glasses I'm probably not a yardstick for proper font-size. ___ 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 ui not working with recent chrome browser
Am 15.03.2015 um 00:30 schrieb a...@gmx-topmail.de: yes, I just did that (Fossil version [6c40678e91] 2015-03-14 13:20:34) and still see the same problem: only part of the html-code is rendered and when I look at the page source that chrome claims to have received that is also incomplete. I have now made some more experiments and found that I have the same problems with internet explorer and opera as well, but with firefox I don't have it. As I saw this right after a chrome update I was mislead to believe it was because of that, but probably it is something completely unrelated to that. Of course that makes me wondering even more whether anyone else has ever seen such behavior... Can't reproduce your new ticket page problem using Fossil 1.32 on Win 7 (64bit). Tested with Default, Xerki and San Francisco skin. Opera 12.17 and IE 11 render fine. Which skin are you using? Did you edit the CSS or the header? ___ 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] GitHub question. Was: Git-v-Fossil.
On Sat, Mar 14, 2015 at 5:28 AM, j. van den hoff veedeeh...@googlemail.com wrote: my understanding was that a github fork is nothing but a clone and not really part of the original project, no? so it really is not comparable to a branch (be it `git' or `fossil'), no? Almost the same as pulling from a clone of a Fossil repo. The key difference is that, in git, the puller can force the in coming commits to be remapped into branches of their own. That is, I could commit my changes to trunk in my clone, then when the other person pulls my changes, she/he can tell git to map my changes into ronw-trunk. ___ 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 ui not working with recent chrome browser
On 3/14/15, a...@gmx-topmail.de a...@gmx-topmail.de wrote: Am 14.03.2015 um 16:30 schrieb Richard Hipp: On 3/14/15, a...@gmx-topmail.de a...@gmx-topmail.de wrote: I am having problems to access my local fossil repositories with a recent versions of chrome, it looks like only part of the html code is served by the standalone webserver. My question is whether this is a known problem and others can verify it with a similar setup. It is not a problem known to me. Can you try it with version 1.32 and let me know if it is still an issue? yes, I just did that (Fossil version [6c40678e91] 2015-03-14 13:20:34) and still see the same problem: only part of the html-code is rendered and when I look at the page source that chrome claims to have received that is also incomplete. I have now made some more experiments and found that I have the same problems with internet explorer and opera as well, but with firefox I don't have it. As I saw this right after a chrome update I was mislead to believe it was because of that, but probably it is something completely unrelated to that. Of course that makes me wondering even more whether anyone else has ever seen such behavior... Do you have an externally-visible repo that we can look at, to try to see what is going wrong? -- 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
[fossil-users] How to change background color dynamically?
Hi, All the skinning going on recently got me interested in tweaking my repo appearance. Not being html/css savvy in the least, I am stumped how to trick the CSS to use a variable background color if remote or localhost? Or I could key on the repo name if I append a 'c' to my clones. I understand TH1 only works inside the header/footer sections, so is it possible to maybe change just their backgrounds? Currently, CSS sets my entire background color. Thanks for Fossil! ___ 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] GitHub question. Was: Git-v-Fossil.
On Sat, Mar 14, 2015 at 8:07 AM, Graeme Pietersz gra...@pietersz.net wrote: The advantage is that anyone can create a Github fork of a public project, work on it, and then submit pull requests, without ever being given commit access to the original repo. You can have untrusted collaborators and review all their contributions before they are merged into your repository - you need not even have had any contact until you get the pull request. What would be really nice would be a distributed version of this, so we could all host our own repos and still collaborate as easily, but I doubt anyone has a sufficient incentive to produce such a thing. Assuming permissions are set appropriately, anyone can clone a Fossil repo, commmit changes to their clone, then send a pull request to the owner of the original repo. The key differences are that Fossil has no mechanism for mapping the incoming commits into branches of their own. The contributor must be sure to commit to her/his own branches. Alternately (and probably a good idea, anyway) is the the puller to clone her/his repo and pull into the clone for review. The recently implemented bundles feature has a mechanism for quarantining commits pulled from the bundle.If this mechanism could be made available for pulls directly from another repo, that would be handy. ___ 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] Git-v-Fossil. Was: Google code shutting down
On Fri, Mar 13, 2015 at 8:46 PM, Timothy Beyer bey...@fastmail.net wrote: At Fri, 13 Mar 2015 20:23:51 -0400, James Moger wrote: You have a great solution. If not then... 5. Corporate users/teams need hooks to integrate with CI notification systems. Partial check. I see there are per-repository hook points, but they seem undeveloped. 6. Corporate users/teams need active notifications: mail, Slack, HipChat, Glip, etc Semi-existing with external tools. See http://core.tcl.tk/akupries/fx/index At least in my view, the ticketing system would be more useful with more hooks for ticket editing and submission. I wrote a vastly more powerful interface to the ticketing system that we use internally, Are the sources of this interface openly visible somewhere, i.e. OSS ? -- Andreas Kupries Senior Tcl Developer Code to Cloud: Smarter, Safer, Faster™ F: 778.786.1133 andre...@activestate.com, http://www.activestate.com Learn about Stackato for Private PaaS: http://www.activestate.com/stackato ___ 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] Google code shutting down
On Sat, Mar 14, 2015 at 12:33 PM, David Mason dma...@ryerson.ca wrote: 1) Fossil's ticket handling is not best-in-class. What are the key features that would make it at least competitive? What features does it have that are already better than most? (I've never used tickets, although the integrated ticket system was one of my reasons for moving from Hg to Fossil.) I will point out that Fossil's ticket subsystem is very customizable. Granted, that requires messing with TH1 code and HTML, but I don't know how much harder that is then customizing Trac or Redmine ticket subsystems. 3 or 4 years ago I posted what I did, but we no longer use that and my copy is is on an USB stick in a box that's hard to get to. But, I was able to implement our issue process flow in TH1. 2) The wiki is not best-in-class. What are the key features it needs? (Merging of changes is certainly one that I see. If multiple people are working on the train to/from work, you don't want last committer wins in your wiki. This is the point of DVCSs.) Yes, that and making sure the P card in wiki artifacts has the correct parent in it. (Last time I checked, the Edit Wiki Page page did not have a (hidden) field to identify the parent artifact.) ___ 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 version 1.32
On 3/14/15, James Turner ja...@calminferno.net wrote: It appears the actual tarballs were also removed. While I understand the reasoning behind this, this will break automated build systems like ports in OpenBSD for stable releases that may reference older versions of fossil. Is there a reason why the tarballs had to be removed? They are still accessible in the old_builds directory. I could move them back. But I decided to make them hard to get to encourage people to upgrade to a version that doesn't have the Ryerson-student-project-eating bug. *If* you can make a compelling argument to move them back, I might. -- 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] GitHub question. Was: Git-v-Fossil.
On 3/14/15, Ron W ronw.m...@gmail.com wrote: The key difference is that, in git, the puller can force the in coming commits to be remapped into branches of their own. That is, I could commit my changes to trunk in my clone, then when the other person pulls my changes, she/he can tell git to map my changes into ronw-trunk. Fossil allows that too. Even if the incoming bundle is on trunk, you can change the branch designation to anything you want after you import the bundle. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil version 1.32
It appears the actual tarballs were also removed. While I understand the reasoning behind this, this will break automated build systems like ports in OpenBSD for stable releases that may reference older versions of fossil. Is there a reason why the tarballs had to be removed? -- James Turner ___ 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] Git-v-Fossil. Was: Google code shutting down
At Sat, 14 Mar 2015 13:33:31 -0700, Andreas Kupries wrote: On Fri, Mar 13, 2015 at 8:46 PM, Timothy Beyer bey...@fastmail.net wrote: At Fri, 13 Mar 2015 20:23:51 -0400, James Moger wrote: You have a great solution. If not then... 5. Corporate users/teams need hooks to integrate with CI notification systems. Partial check. I see there are per-repository hook points, but they seem undeveloped. 6. Corporate users/teams need active notifications: mail, Slack, HipChat, Glip, etc Semi-existing with external tools. See http://core.tcl.tk/akupries/fx/index At least in my view, the ticketing system would be more useful with more hooks for ticket editing and submission. I wrote a vastly more powerful interface to the ticketing system that we use internally, Are the sources of this interface openly visible somewhere, i.e. OSS ? Unfortunately, not yet. At some point I am going to try to persuade my boss of the merits of releasing the source code, particularly to the ticket search capabilities. Tim ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Footer missing on www.fossil-scm.org?
Hello, I just browsed to: https://www.fossil-scm.org/fossil/timeline?y=ci and there is no footer... Not sure if this is due to the skin that is currently enabled on it, or some other cause, but I thought I would point it out. Andy -- TAI64 timestamp: 40005505086d ___ 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] Git-v-Fossil. Was: Google code shutting down
Tim wrote: At Sat, 14 Mar 2015 13:33:31 -0700, Andreas Kupries wrote: On Fri, Mar 13, 2015 at 8:46 PM, Timothy Beyer bey...@fastmail.net wrote: At least in my view, the ticketing system would be more useful with more hooks for ticket editing and submission. I wrote a vastly more powerful interface to the ticketing system that we use internally, Are the sources of this interface openly visible somewhere, i.e. OSS ? Unfortunately, not yet. Sorry to hear that. At some point I am going to try to persuade my boss of the merits of releasing the source code, particularly to the ticket search capabilities. IIRC Richard is experimenting with general searching of fossil repos via the sqlite FTS, i.e. commits, wiki pages, tickets, etc. -- So long, Andreas Kupries akupr...@shaw.ca http://www.purl.org/NET/akupries/ Developer @ http://www.activestate.com/ EuroTcl 2015, June 20-21, Colgne/DE, http://www.eurotcl.tcl3d.org/ 22'nd Tcl/Tk Conference: Oct 19-23, Manassas, VA, USA --- ___ 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] Footer missing on www.fossil-scm.org?
Thus said Andy Bradford on 14 Mar 2015 22:19:22 -0600: https://www.fossil-scm.org/fossil/timeline?y=ci and there is no footer... Oh, I see the problem. The text in the footer is some color of grey, and there is no body color defined in www.fossil-scm.org's CSS, and it just happens to match the background color of my browser, so it was hidden. If I use the mouse to highlight the text area, it shows up. Andy -- TAI64 timestamp: 400055050a9d ___ 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] GitHub question. Was: Git-v-Fossil.
On Sat, Mar 14, 2015 at 10:28 AM, j. van den hoff veedeeh...@googlemail.com wrote: really a test case for how does github feel to a newbie. answer: awkward, to say the very least. FWIW i have had to use it a dozen times and still feel that way. this is quite different to first time encounter with `fossil'. so one probably should not look to closely on github on how to improve `fossil'. ;-) LOL! The network is primarily intended to show fork-related relationships. i.e. whose fork was created/merged at what point. In a way it's similar to the branch handling in fossil's timeline. github's workflow encourages using forks rather than branches (the end effect is similar, since a fork can be merged in at any time). my understanding was that a github fork is nothing but a clone and not really part of the original project, no? Correct, but... so it really is not comparable to a branch (be it `git' or `fossil'), no? a git fork can be pulled (via a pull request) into the original just like merging a branch, so the the effect is similar (not identical). just my 2c (probably explaining the very obvious ;-)) Nothing about git is obvious ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] Google code shutting down
On 14/03/15 05:20, Warren Young wrote: On Mar 13, 2015, at 4:22 PM, Graeme Pietersz gra...@pietersz.net wrote: On 14/03/15 03:01, Warren Young wrote: I believe that once you extract the hosting services from the comparison, Fossil comes out quite a bit ahead of Git. Even without hosted services, Git still has integration with the likes of Trac and Redmine, and , as James Moger pointed out, things like Gitlab, all of which you can host yourself. Yes, and you’re going to find out that setting them up is quite a lot more difficult than setting up Fossil. Having set up Trac once, I am very much aware of that. I did say that the trade-off is more work to set up vs a more user friendly system once set up. You’re trying to compare a hosted service, staffed by a full-time set of sysadmins and designers and such to Fossil. It would be just as unfair to try to compare ChiselApp to some Git+Trac+MediaWiki lash-up. Why would you need Media Wiki? Trac has a wiki, and it can host multiple repos (albeit with no way of giving users different access to different projects). Redmine can do the same without that limitation. I have not looked at Gitlab etc. properly, but they also all seem to have those features. Why is it a lash-up? Trac now officially supports Git, so does Redmine. Things like Gitlab and Gitblit obviously do. Comparing ChiselApp (unless its improved a lost since the last time I used it) to Git + Trac, the latter has a better issue tracker and wiki (because the ChiselApp equivalents are just the Fossil ones). Git has 1) multiple hosted services better than ChiselApp *and* 2) multiple issue tracker + wiki web apps you can install yourself that are better than those that come with Fossil *and* 3) the web apps are better than ChiselApp bar the initial trouble of installing and configuring them. It is not a matter of blame, but of a real disadvantage. More like a trade-off, I think. If X has a feature that Y does not it is a disadvantage, not a trade off. For me, it rules out using Fossil tickets as a way of clients reporting issues. ChromeOS seems to be rather an odd choice for a development machine Mostly I did it just to see if it could be done, but Scott’s right, it makes a fine self-contained offline-editable wiki. Another practical use is on a Chromebook set up with Crouton [1] where actual software development and such takes place inside the chroot box, but you maintain a separate clone of the software repo outside the box on the ChromeOS side for answering tech support questions when you don’t want to bother firing up Crouton. Crouton looks very useful, and that is a good use case for using something that is simple to compile. Personally I would probably just install Ubuntu and use it, but that is a matter of personal preference. You build the fossil binary while inside the chroot box, then scp it out before shutting Crouton down. Crouton + Ubuntu ends up being a cross-compilation environment for ChromeOS. And yes, I have used a Chromebook + Crouton for actual software development. For $200 and 3 pounds in my EDC bag, it’s a fine setup for cases where I don’t want to drag along the full-size laptop. To do better than a standard Chromebook for weight and size, you have to pay many times more for a Pixel or the new MacBook Nothin’. [1] https://github.com/dnschneid/crouton ___ 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] GitHub question. Was: Git-v-Fossil.
On Sat, Mar 14, 2015 at 5:05 AM, Richard Hipp d...@sqlite.org wrote: I tried going to the network graph (https://github.com/mackyle/sqlite/network) which seems similar to the Fossil timeline graph, only sideways. The network is primarily intended to show fork-related relationships. i.e. whose fork was created/merged at what point. In a way it's similar to the branch handling in fossil's timeline. github's workflow encourages using forks rather than branches (the end effect is similar, since a fork can be merged in at any time). Am I wrong to think that clicking through the changes in a project (not necessarily from the beginning, but from some signification event, say the most recent release) in chronological order is something that people might commonly want to do? It's possibly a case of not missing what one never had. Some tools, e.g. Google Code, offer the ability to move forward and backward through commit numbers. e.g. see the links near the top/right of this SVN browser: https://code.google.com/p/v8-juice/source/browse/convert/include/cvv8/XTo.hpp?r=2070 But that's at the file level. It has a timeline-like view, but it's not nearly as informative as fossil's: https://code.google.com/p/v8-juice/source/list (But it's easy enough to find the start of the project there.) Haven't ever spent enough time in github to notice if/how it does something similar. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] GitHub question. Was: Git-v-Fossil.
On Sat, 14 Mar 2015 10:18:35 +0100, Stephan Beal sgb...@googlemail.com wrote: On Sat, Mar 14, 2015 at 5:05 AM, Richard Hipp d...@sqlite.org wrote: I tried going to the network graph (https://github.com/mackyle/sqlite/network) which seems similar to the Fossil timeline graph, only sideways. I needed to use github only once, fortunately, when I wanted to contribute a small patch to `asciidoc', so I am really a test case for how does github feel to a newbie. answer: awkward, to say the very least. this is quite different to first time encounter with `fossil'. so one probably should not look to closely on github on how to improve `fossil'. ;-) The network is primarily intended to show fork-related relationships. i.e. whose fork was created/merged at what point. In a way it's similar to the branch handling in fossil's timeline. github's workflow encourages using forks rather than branches (the end effect is similar, since a fork can be merged in at any time). my understanding was that a github fork is nothing but a clone and not really part of the original project, no? so it really is not comparable to a branch (be it `git' or `fossil'), no? in my (probably naive or wrong) view github seems nothing more than a way to manage changes in different clones of a project which are suggested for cherry-pick merge into the main repo (plus a lot of eye candy I for one find distracting rather than helpful). so github as far as I can see is only a metastructure on top of `git' and this functionality might (or might not) be mimicked as part of `fossil' or via some sort of `fossilhub'. I see that github is immensely successful so no sense arguing that something like that seems desirable. just my 2c (probably explaining the very obvious ;-)) j. re Am I wrong to think that clicking through the changes in a project (not necessarily from the beginning, but from some signification event, say the most recent release) in chronological order is something that people might commonly want to do? It's possibly a case of not missing what one never had. Some tools, e.g. Google Code, offer the ability to move forward and backward through commit numbers. e.g. see the links near the top/right of this SVN browser: https://code.google.com/p/v8-juice/source/browse/convert/include/cvv8/XTo.hpp?r=2070 But that's at the file level. It has a timeline-like view, but it's not nearly as informative as fossil's: https://code.google.com/p/v8-juice/source/list (But it's easy enough to find the start of the project there.) Haven't ever spent enough time in github to notice if/how it does something similar. -- Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ 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] GitHub question. Was: Git-v-Fossil.
Stephan Beal sgb...@googlemail.com writes: a git fork can be pulled (via a pull request) into the original just like merging a branch, so the the effect is similar (not identical). These days most of the FOSS is hosted at github and for someone wanting to contribute to usual scenario is: 1) clone original repo 2) create feature/fix branch locally 3) hack and rebase fix/feature on original's master 4) submit PR 5) fix/feature is reviewed 6) if the fix/feature needs more work go to 3) 7) fix/feature is merged in master Now, if someone wants to maximize usage of Fossil and minimize usage of Git, what can be improved in Fossil in regard or what is the recommended workflow to be practiced? Sincerely, Gour -- Everyone is forced to act helplessly according to the qualities he has acquired from the modes of material nature; therefore no one can refrain from doing something, not even for a moment. ___ 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] GitHub question. Was: Git-v-Fossil.
IMO, everything is in reverse. GitHub is not popular, because Git is great SCM. Git is popular because is used by GitHub! Notice that GitHub is not only repository hosting. It is a social network for developers. That is why it is popular. And every SCM used in such popular social network will become popular on its own. So, Fossil can do nothing in the field of SCM design. But maybe it can do something in the field of the social networking? I am not social network user and slightly imagine what such users need. But, for example fossil can provide some way to connect the stand alone repositories and developers in some kind of distributed peer-to-peer network and to provide some interaction - I don't know - maybe some voting, messaging, clone tracking, collaborative environment, pull requests, whatever will turn a heap of independent repositories into mutually connected developers network. On Sat, 14 Mar 2015 00:05:07 -0400 Richard Hipp d...@sqlite.org wrote: I periodically go to sites like GitHub looking for ideas on how Fossil might be improved. So just now I was browsing the SQLite mirror that somebody has put there. And I asked the simple question: How did this project start? (I already know the answer, of course, but I'm curious to see how somebody would figure it out if they were not the original author.) So I locate the initial check-in here: https://github.com/mackyle/sqlite/commit/a3b0e7bbb4e863e1f46ec7de5967e61cc57c8c4b Finding that check-in was an adventure in and of itself. Is there an easy way that I overlooked to find the start of a project in GitHub? But now that I'm on the initial check-in, how do I get to the second check-in? How do I find what comes next? It seems like every check-in information page has a parent link. But I can't find any children links. What am I missing? When reviewing the changes to a project, how to you move forward in time? I tried going to the network graph (https://github.com/mackyle/sqlite/network) which seems similar to the Fossil timeline graph, only sideways. But that graph only seems to go back to 2011-06-03. In other words, the graph only shows about the 5000 most recent changes. How do I go back further in time? Am I wrong to think that clicking through the changes in a project (not necessarily from the beginning, but from some signification event, say the most recent release) in chronological order is something that people might commonly want to do? -- 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 -- http://fresh.flatassembler.net http://asm32.info John Found johnfo...@asm32.info ___ 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] GitHub question. Was: Git-v-Fossil.
On 14/03/15 15:04, Stephan Beal wrote: On Sat, Mar 14, 2015 at 10:28 AM, j. van den hoff veedeeh...@googlemail.com mailto:veedeeh...@googlemail.com wrote: really a test case for how does github feel to a newbie. answer: awkward, to say the very least. FWIW i have had to use it a dozen times and still feel that way. I disagree: I found Github easy to use. What I found difficult was the Git command line, and the rather complex process it imposes. this is quite different to first time encounter with `fossil'. so one probably should not look to closely on github on how to improve `fossil'. ;-) LOL! The network is primarily intended to show fork-related relationships. i.e. whose fork was created/merged at what point. In a way it's similar to the branch handling in fossil's timeline. github's workflow encourages using forks rather than branches (the end effect is similar, since a fork can be merged in at any time). my understanding was that a github fork is nothing but a clone and not really part of the original project, no? Correct, but... so it really is not comparable to a branch (be it `git' or `fossil'), no? a git fork can be pulled (via a pull request) into the original just like merging a branch, so the the effect is similar (not identical). The advantage is that anyone can create a Github fork of a public project, work on it, and then submit pull requests, without ever being given commit access to the original repo. You can have untrusted collaborators and review all their contributions before they are merged into your repository - you need not even have had any contact until you get the pull request. What would be really nice would be a distributed version of this, so we could all host our own repos and still collaborate as easily, but I doubt anyone has a sufficient incentive to produce such a thing. just my 2c (probably explaining the very obvious ;-)) Nothing about git is obvious ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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] GitHub question. Was: Git-v-Fossil.
On 14 March 2015 at 05:07, Graeme Pietersz gra...@pietersz.net wrote: On 14/03/15 15:04, Stephan Beal wrote: On Sat, Mar 14, 2015 at 10:28 AM, j. van den hoff veedeeh...@googlemail.com wrote: really a test case for how does github feel to a newbie. answer: awkward, to say the very least. FWIW i have had to use it a dozen times and still feel that way. I disagree: I found Github easy to use. What I found difficult was the Git command line, and the rather complex process it imposes. So github simplified a complicated process. this is quite different to first time encounter with `fossil'. so one probably should not look to closely on github on how to improve `fossil'. ;-) LOL! The network is primarily intended to show fork-related relationships. i.e. whose fork was created/merged at what point. In a way it's similar to the branch handling in fossil's timeline. github's workflow encourages using forks rather than branches (the end effect is similar, since a fork can be merged in at any time). my understanding was that a github fork is nothing but a clone and not really part of the original project, no? Correct, but... so it really is not comparable to a branch (be it `git' or `fossil'), no? a git fork can be pulled (via a pull request) into the original just like merging a branch, so the the effect is similar (not identical). The advantage is that anyone can create a Github fork of a public project, work on it, and then submit pull requests, without ever being given commit access to the original repo. You can have untrusted collaborators and review all their contributions before they are merged into your repository - you need not even have had any contact until you get the pull request. Fossil has bundle: https://www.fossil-scm.org/fossil/help?cmd=bundle But this means you need to email your changes to the devs. If you were to only use git, could someone submit pull requests without access to the repo? What would be really nice would be a distributed version of this, so we could all host our own repos and still collaborate as easily, but I doubt anyone has a sufficient incentive to produce such a thing. just my 2c (probably explaining the very obvious ;-)) Nothing about git is obvious ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] GitHub question. Was: Git-v-Fossil.
On Sat, Mar 14, 2015 at 1:58 PM, Graeme Pietersz gra...@pietersz.net wrote: There is a long and interesting discussion between Linux Torvalds and others about the merits of the Github approach here: https://github.com/torvalds/linux/pull/17#issuecomment-5654674 If that can be called a discussion. It's Linus in his typically tactless, holier-than-thou-and-everything-else form. i, for one, am glad that _our_ Benevolent Dictator behaves like an empathic human being in public. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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 ui not working with recent chrome browser
I am having problems to access my local fossil repositories with a recent versions of chrome, it looks like only part of the html code is served by the standalone webserver. My question is whether this is a known problem and others can verify it with a similar setup. This is what does show the problems for me (on Windows 7): fossil init test.fossil fossil ui test.fossil then use chrome version 41.0.2272.89 m to navigate to e.g. the new ticket page, of which only the summary inputfield and Type-combobox are shown. Same page and setup shows correctly with e.g. firefox. I see the same problem when accessing a fossil repo served with the standalone server from a linux machine (which I accessed from the same windows box with the same browser version via a ssh-tunnel, if that matters). Other public fossil sites seem to work correctly with that chrome version, so I guess it could be something which only happens when using the standalone server. I've seen this with fossil versions 1.31 and also 1.28, others I haven't tested. As I can just use another browser and it also seems to work when using other web server setups it isn't a big problem for me, but I thought it might be worth reporting... Albert ___ 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] GitHub question. Was: Git-v-Fossil.
On 14/03/15 17:55, jungle Boogie wrote: On 14 March 2015 at 05:07, Graeme Pietersz gra...@pietersz.net wrote: On 14/03/15 15:04, Stephan Beal wrote: On Sat, Mar 14, 2015 at 10:28 AM, j. van den hoff veedeeh...@googlemail.com wrote: really a test case for how does github feel to a newbie. answer: awkward, to say the very least. FWIW i have had to use it a dozen times and still feel that way. I disagree: I found Github easy to use. What I found difficult was the Git command line, and the rather complex process it imposes. So github simplified a complicated process. Yes, a lot for some people - e.g. someone who wants to start contributing to an open source project. this is quite different to first time encounter with `fossil'. so one probably should not look to closely on github on how to improve `fossil'. ;-) LOL! The network is primarily intended to show fork-related relationships. i.e. whose fork was created/merged at what point. In a way it's similar to the branch handling in fossil's timeline. github's workflow encourages using forks rather than branches (the end effect is similar, since a fork can be merged in at any time). my understanding was that a github fork is nothing but a clone and not really part of the original project, no? Correct, but... so it really is not comparable to a branch (be it `git' or `fossil'), no? a git fork can be pulled (via a pull request) into the original just like merging a branch, so the the effect is similar (not identical). The advantage is that anyone can create a Github fork of a public project, work on it, and then submit pull requests, without ever being given commit access to the original repo. You can have untrusted collaborators and review all their contributions before they are merged into your repository - you need not even have had any contact until you get the pull request. Fossil has bundle: https://www.fossil-scm.org/fossil/help?cmd=bundle But this means you need to email your changes to the devs. If you were to only use git, could someone submit pull requests without access to the repo? Git provides some support for generating pull requests: http://git-scm.com/docs/git-request-pull but, as far as I know, it does nothing to help you communicate them or accept them. You can email the generated pull request, which contains a URL for pulling the relevant changes. There is a long and interesting discussion between Linux Torvalds and others about the merits of the Github approach here: https://github.com/torvalds/linux/pull/17#issuecomment-5654674 What would be really nice would be a distributed version of this, so we could all host our own repos and still collaborate as easily, but I doubt anyone has a sufficient incentive to produce such a thing. just my 2c (probably explaining the very obvious ;-)) Nothing about git is obvious ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ 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 skin: Blitz
On 3/13/15, James Moger james.mo...@gmail.com wrote: I decided to make some time to play with your DVCS (being a fan of SCM) and to whip-up a new skin accompanying resources to contribute to your effort. https://www.fossil-scm.org/fossil/artifact/f10bb06c1015336a?ln=745 I sometimes have browser windows that are significantly wider than 900px. (And also sometimes significantly narrow.) Would it mess up the look to remove the upper bound on the width? I would have thought that a lower bound would be more important. What's the rationale here? -- 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] Google code shutting down
Hi Dave, On 14 March 2015 at 09:33, David Mason dma...@ryerson.ca wrote: 1) Fossil's ticket handling is not best-in-class. What are the key features that would make it at least competitive? What features does it have that are already better than most? (I've never used tickets, although the integrated ticket system was one of my reasons for moving from Hg to Fossil.) You may have seen this post my Ron earlier in the week: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg19451.html A query builder seems like something that would bridge the gap and help people out. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] hooks in Fossil
mario ma...@include-once.org writes:
Basically you'd prepare `th1-setup` (Admin Settings) with a script
such as:
proc command_notify {} {
if {$::cmd_name eq push} {
tclInvoke exec ./your/public-update-script
}
}
Am I right that above would make *every* invocation of +push' to invoke
updating script?
That's something which I certainly do not want, having need to hook
e.g. rsync only for specific repo(s).
Sincerely,
Gour
--
One who restrains his senses, keeping them under full control,
and fixes his consciousness upon Me, is known as a man of
steady intelligence.
___
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 skin: Blitz
Perfect skin. I really like `login` button positioning. One thing though,
shouldn't it be
.mainmenu li a{padding: 10px 15px;}
instead of
.mainmenu li {padding: 10px 15px;}
as I expect to see clickable object as li background changes
On Fri, Mar 13, 2015 at 9:11 PM, James Moger james.mo...@gmail.com wrote:
Hello Fossil community,
My name is James and I am not a Fossil user, I'm a git user. I also
happen to run a moderately successful on-premise Git server project not
unlike Fossil, http://gitblit.com. But that is not why I am writing you.
I've long been an admirer of Fossil's integrated approach and I
periodically check-in to see how things are moving along in this project.
I see that in the last few releases Fossil has been getting a lot more
competent and that is great.
I decided to make some time to play with your DVCS (being a fan of SCM)
and to whip-up a new skin accompanying resources to contribute to your
effort. This theme, Blitz, is demonstrated here:
http://dev.gitblit.com:8080/cgi-bin/repo/fossil
http://dev.gitblit.com:8080/cgi-bin/repo/sqlite
If you've ever seen Gitblit, then this theme will feel comfortable,
although it is specialized for Fossil and shares little of the same CSS
code.
Blitz has two variants (with logo without logo). It includes an
alternative Ticket page layout and several image resources which may be of
use to other skins.
@Richard: I've emailed a signed CLA and a bundle for your review and
integration consideration.
I hope to contribute more in the future.
-J
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
I remain,
Arseniy Terekhin
___
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] hooks in Fossil
Abilio Marques abili...@gmail.com writes: You can hook the commit: admintransferscommit , but you'll need a way to make it copy the files. I have a similar setup with LaTeX generating a PDF every time I commit a change to the source. For this purpose I built an exec command for TH1. By pure luck I've just sent a patch for my latest version, under an email labeled TH1 exec. Maybe you can take a look at it, include it in the fossil source code, compile, and use it. If you do, any comments to improve it are welcomed. Thanks a lot, I'll take a look. I guess you can write a shell script (or bat in windows) and use something like rsync... Something like: rsync -a public/ remotedir is good enough. Sincerely, Gour -- When your intelligence has passed out of the dense forest of delusion, you shall become indifferent to all that has been heard and all that is to be heard. ___ 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 skin: Blitz
On 3/13/15, James Moger james.mo...@gmail.com wrote: @Richard: I've emailed a signed CLA and a bundle for your review and integration consideration. The new skin (both the with and without logo variants) are now merged onto trunk. I hope to contribute more in the future. Please do. -- 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] New skin: Blitz
Hi James, Richard, On 14 March 2015 at 08:31, Richard Hipp d...@sqlite.org wrote: On 3/14/15, Richard Hipp d...@sqlite.org wrote: On 3/13/15, James Moger james.mo...@gmail.com wrote: @Richard: I've emailed a signed CLA and a bundle for your review and integration consideration. The new skin (both the with and without logo variants) are now merged onto trunk. The new skin can now also be previewed on-line at: https://www.fossil-scm.org/blitz/doc/trunk/www/index.wiki I like the new skin, especially the clever rss icon placement. I wear glasses and I'm long overdue for an optometrist appointment, but I find the diffs rather too small to read. https://www.fossil-scm.org/blitz/info/39f084cf2cf8791d https://www.fossil-scm.org/fossil/info/39f084cf2cf8791d vs. https://www.fossil-scm.org/skin2/info/39f084cf2cf8791d Andrew updated the latter skin from .75em to .85 and it makes all the difference: https://www.fossil-scm.org/skin2/info/56f9d72933fe966b Attached is what the diff looks like for blitz (and pretty much identical for default) in google chrome on windows. No, I didn't zoom to outterspace, my browser is at 100%. Does anyone else have issues reading diffs? -- D. Richard Hipp d...@sqlite.org -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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 version 1.32
Fossil version 1.32 is now available on the download page: https://www.fossil-scm.org/download.html The new builds all use version numbers in their names instead of dates. All previous builds have been removed from the download page due to the Ryerson student project problem. Please encourage everyone you know to update to version 1.32. Please report any problems in the new build to this list. Thanks. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] New skin: Blitz
On 3/14/15, Richard Hipp d...@sqlite.org wrote: On 3/13/15, James Moger james.mo...@gmail.com wrote: @Richard: I've emailed a signed CLA and a bundle for your review and integration consideration. The new skin (both the with and without logo variants) are now merged onto trunk. The new skin can now also be previewed on-line at: https://www.fossil-scm.org/blitz/doc/trunk/www/index.wiki -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil ui not working with recent chrome browser
On 3/14/15, a...@gmx-topmail.de a...@gmx-topmail.de wrote: I am having problems to access my local fossil repositories with a recent versions of chrome, it looks like only part of the html code is served by the standalone webserver. My question is whether this is a known problem and others can verify it with a similar setup. It is not a problem known to me. Can you try it with version 1.32 and let me know if it is still an issue? This is what does show the problems for me (on Windows 7): fossil init test.fossil fossil ui test.fossil then use chrome version 41.0.2272.89 m to navigate to e.g. the new ticket page, of which only the summary inputfield and Type-combobox are shown. Same page and setup shows correctly with e.g. firefox. I see the same problem when accessing a fossil repo served with the standalone server from a linux machine (which I accessed from the same windows box with the same browser version via a ssh-tunnel, if that matters). Other public fossil sites seem to work correctly with that chrome version, so I guess it could be something which only happens when using the standalone server. I've seen this with fossil versions 1.31 and also 1.28, others I haven't tested. As I can just use another browser and it also seems to work when using other web server setups it isn't a big problem for me, but I thought it might be worth reporting... Albert ___ 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] New skin: Blitz
On 13/03/15 19:11, James Moger wrote: [---] Blitz has two variants (with logo without logo). It includes an alternative Ticket page layout and several image resources which may be of use to other skins. Would you be willing to change the upper-case 'A-F' in hex digits to lower-case in the timeline? -- Kind Regards, Jan ___ 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] Google code shutting down
Thank you Graeme for your thought-provoking post. It seems most challenges and rebuttals have played out. If anyone was mining this thread for ways to improve fossil, I think they'd see 2 things: 1) Fossil's ticket handling is not best-in-class. What are the key features that would make it at least competitive? What features does it have that are already better than most? (I've never used tickets, although the integrated ticket system was one of my reasons for moving from Hg to Fossil.) 2) The wiki is not best-in-class. What are the key features it needs? (Merging of changes is certainly one that I see. If multiple people are working on the train to/from work, you don't want last committer wins in your wiki. This is the point of DVCSs.) ../Dave ___ 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] GitHub question. Was: Git-v-Fossil.
Thus said Richard Hipp on Sat, 14 Mar 2015 00:05:07 -0400: Am I wrong to think that clicking through the changes in a project (not necessarily from the beginning, but from some signification event, say the most recent release) in chronological order is something that people might commonly want to do? It's certainly something I commonly want to do, and sorely miss when I have to use github. I use gitk to fill the voi d, but it too is lacking. I prefer that the tools I use help me reason effectively about the data I'm looking at and something like clicking through changes helps me do this for a series of checkins. But I'm just expressing my bias---I don't know what other people might commonly want to do. :-) Andy -- TAI64 timestamp: 400055047499 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
