http://blog.gmane.org/gmane.comp.version-control.fossil-scm.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9235 <pre>Hello. Is it possible to get a more "raw" list than 'fossil timeline before 2012-05-27 -t ci' out of the command line tool? Would prefer a straight list of newline-separated hash values. </pre> org.fossil-scm.fossil-users-fAjmDXfYvhs< at >public.gmane.org 2012-05-26T21:34:48 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9233 <pre>When I was just starting with fossil I hadn't grasped the distinction between the repository and a checkout so this error message was confusing to me. I read it as "you can't do this operation within an open checkout", rather than the intended "you are not currently within an open checkout". I think the message should be amended to something like "current directory is not within an open checkout". </pre> Noam Postavsky 2012-05-26T20:53:27 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9209 <pre>Hello. 1) I created a private branch, made several commits, and then merged the private branch with the current trunk. Rather than seeing the commits I made on the private branch in the timeline for the trunk, I only see the one large commit resulting from accumulating all the smaller commits into one when merging. Is it possible to avoid squashing all private commits into one? 2) Additionally, as auto-sync was enabled, the large commit was pushed to a remote. I realize it's not possible to rewrite history (nor would I want to), but is there some way to push any changes I make whilst trying to sort out item 1 above (so that the private commits are visible)? </pre> org.fossil-scm.fossil-users-fAjmDXfYvhs< at >public.gmane.org 2012-05-25T15:42:37 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9206 <pre>Hi, Small esthetic bug here... In one of our repository, we have some ".locale" translation files (utf-8 encoded) and have Chinese character in it. When doing sbsdiff from web interface, like that contain Chinese character are miss-aligned. See screenshot... </pre> Martin Gagnon 2012-05-24T13:25:32 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9204 <pre>Hi! 1.22 ChangeLog: "Add the ability to run TH1 scripts after sync requests" I'm a bit lost -- where can I find more infrmation about that new feature? Examples? What to do with it? Can I for example use it to have some basic commit hooks? Thanks Tino </pre> Tino Lange 2012-05-24T08:25:33 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9194 <pre>Uncovered a bug. In this case, two users working in their own fossil work areas independently created a file with the same name. Each file is unique. Fossil identifies that there is a conflict, but does NOT attempt to merge the files. Commands to duplicate issue follow: -jmg ##Script started on Wed 23 May 2012 10:22:54 AM MST fossil init test.fossil project-id: e3d111bd110a8cfccd49f5fda722dbafb2c05e72 server-id: 54ac75ed1002c3454a9d574c8848729720f6d867 admin-user: jmgedge (initial password is "2a508f") mkdir area{1,2} cd ./area1/ fossil open ../test.fossil echo "line1_area1" &gt;&gt; file_a.txt echo "line2_area1" &gt;&gt; file_a.txt echo "line3_area1" &gt;&gt; file_a.txt cd ../area2/ fossil open ../test.fossil echo "line1_area2" &gt;&gt; file_a.txt echo "line2_area2" &gt;&gt; file_a.txt echo "line3_area2" &gt;&gt; file_a.txt fossil set gmerge 'xxdiff "%original" "%baseline" "%merge" -M "%output"' cd ../area1/ fossil add file_a.txt ADDED file_a.txt fossil commit -m "area1 initial commit" New_Version: 025b2bc66c831dcb</pre> Justin Gedge 2012-05-23T20:16:08 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9190 <pre>Has anyone noticed this? When Explorer of WinXP opens a zip created by fossil zip export, it shows a zero-sized file for every subfolder in the zip. Explorer of Win7 does not have this problem, and neither does 7z. However, would it be possible to fix this annoyance for remaining XP users? Thanks, Pavel A. </pre> Pavel Aronsky 2012-05-23T17:56:09 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9164 <pre>Hello, stuff happens, and it turns out that now I have finished integrating my markdown library (libupskirt) into fossil. And I really mean "integrating", that is using struct Blob as dynamic buffers and other idioms. I used it to translate *.mkd and *.markdown embedded docs in a similar way as *.wiki are currently translated. The end result is available in the "markdown" branch at http://fossil.instinctive.eu/fossil-scm/doc/trunk/www/index.wiki A demo repository using that extended fossil, with texts provided by bapt, can be found at: http://fossil.instinctive.eu/markdown-examples/doc/tip/README.mkd http://fossil.instinctive.eu/markdown-examples/doc/tip/FAQ.mkd As far as I can tell through visual inspection, the markdown engine passes the official markdown test suite. I don't publish the result becasue I haven't found any licence for the test suite, so I guess redistributing it is illegal. The current implementation supports only vanilla markdown along with talbe (using PHP-Markdown-Extra syntax). Qui</pre> Natacha Porté 2012-05-23T15:53:20 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9152 <pre>Hello, in fossil, can I sign check-ins *after* having done the checkin, as we can edit commit logs, etc? If not, it would be very nice. Regards, Lluís. </pre> Lluís Batlle i Rossell 2012-05-22T14:33:22 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9151 <pre>Noticed these in my config settings on a new repository. I'm guessing these are the hooks I've long wanted? Are there any docs/examples for these? I'd like to hit the URL of a Jenkins CI system whenever a repository gets pushed to, thus triggering a rebuild. Is this possible? Thanks. </pre> Nolan Darilek 2012-05-22T13:34:51 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9137 <pre>Hi all, Please consider the following test (in Linux on version 1.22): % mkdir dir_a % ln -s dir_a dir_b % touch dir_a/foo % fossil add dir_a/foo ADDED dir_a/foo % fossil commit dir_a/foo -m 'adding test' ADDED dir_a/foo ... % fossil ann dir_a/foo % fossil ann dir_b/foo fossil: no such file: dir_b/foo I realize that fossil probably only responds to the "real" managed path in dir_a. But this situation may be confusing... thanks James _______________________________________________ fossil-users mailing list fossil-users-RyYwo1q5J+rPvulMB6uEI2D2FQJk+8+b&lt; at &gt;public.gmane.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users </pre> James Masters 2012-05-15T17:51:27 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9118 <pre>The latest version of Fuel has been released! Precompiled binaries for Windows and OSX are available at: http://code.google.com/p/fuel-scm/downloads This release adds support for stashes, basic drag and drop, a portable mode as well as various bug fixes and UI improvements. For a more detailed change log have a look at: https://chiselapp.com/user/karanik/repository/fuel/doc/v0.9.6/doc/Changes.txt Please give it a try and let me know if you find any problems. Comments, feature suggestions, patches are also welcome. Thanks Kostas </pre> Kostas Karanikolas 2012-05-13T06:33:35 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9114 <pre>Hi, Our IT team is moving to Zscaler proxy and testing fossil through this proxy fails with '400 Bad request'. Using old proxy server (still active, not sure what type) works. IT guys told me that CONNECT method will work, not sure what it is. Any help possible? - Altu _______________________________________________ fossil-users mailing list fossil-users-RyYwo1q5J+rPvulMB6uEI2D2FQJk+8+b&lt; at &gt;public.gmane.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users </pre> Urmil Parikh 2012-05-11T12:02:14 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9104 <pre> An aside: My main motivation is to avoid having to select Trac in the near term merely because of Fossil usability issues. If I do have to temporarily select Trac while Fossil usability matures, it would be a massive benefit if there would one day also be a way to import a Trac system into Fossil (code, comments, bugs, wiki, etc.) with a single (well, a few) reliable commands. Ø I you just mean the wiki, there are CLI-mode commands for exporting and importing them to/from files. See create/export/commit subcommands to "fossil wiki". No, I mean EVERYTHING essential in a Trac project, so that Trac itself could be turned off, disconnected, deleted and forgotten in favor of Fossil. _______________________________________________ fossil-users mailing list fossil-users-RyYwo1q5J+rPvulMB6uEI2D2FQJk+8+b&lt; at &gt;public.gmane.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users </pre> Cunningham, Robert 2012-05-10T15:56:43 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9101 <pre>a hypothetical, admittedly somewhat far-out, use case for fossil... Use the JSON API to transfer wiki pages (or other information) between a repo and Google Drive: https://developers.google.com/drive/v1/reference/ i don't yet know if the GDrive API allows updating of existing Google Spreadsheets or Google Docs, but if it does then those could be populated/amended based on e.g. commit log or ticket pollers. Or the other way around: they could be periodically exported from GDrive to Fossil (that work currently work for wiki pages, but the JSON API can't yet commit non-wiki content, and possibly won't ever be able to commit _binary_ content). Not that i'll ever get around to actually trying that out, but: a) "Hope dies last", as the Berliners say b) Maybe one of you younger folks with an over-abundance of energy might find that to be an interesting experiment. Happy Hacking! </pre> Stephan Beal 2012-05-09T18:06:34 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9078 <pre>Is there some easy way to find "orphaned" wiki pages? That means: pages which cannot be reached from another page. I'm working with a person who is prolifically inserting wiki pages, but not making anything link to them ... it's driving me crazy, and I'll eventually train her to stop that, but in the meantime I want to find all such pages and link them into the document tree. Suggestions? Thanks, Ron </pre> Ron Aaron 2012-05-08T03:25:06 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9068 <pre>First of all thanks for a great piece of software, and all the constructive dialogue on the mailing list. It is quite educative! Whilst reading the wiki I noticed a minor bug - that pictures are not loaded consistently when reading pages. I have taken 4 screenshots from http://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki by re-loading (F5) the pages a few times, to illustrate the inconsistency. (All attached). I hope it may help? Kind Regards </pre> Bjorn Madsen 2012-05-07T19:56:15 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9064 <pre>Hi, all! Just out of curiosity... how old are the oldest fossil repos out there? Here are the oldest i personally know about: (times taken from the /stat pages within the last 15 minutes) - Fossil itself: 1753 days or approximately 4.92 years - Oldest repo of mine i could find: 1550 days or approximately 4.24 years - Oldest repo i actively maintain: 1234 days or approximately 3.38 years i must have a slightly older one _somewhere_, because i've been using Fossil since the Christmas holidays of 2007 (and rarely delete anything). The sqlite3 repo says it's 4362 days/11.94 years old, but that includes many years of activity before the fossil import, and i'm not sure when sqlite3 made the jump to fossil (coming full circle in its evolution). :-? </pre> Stephan Beal 2012-05-07T18:17:42 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9054 <pre> [pjb&lt; at &gt;kuiper :0 patchwork]$ fossil push Server: http://fossil.informatimago.com:8002/patchwork Bytes Cards Artifacts Deltas Sent: 268 4 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 386 bytes sent, 276 bytes received [pjb&lt; at &gt;kuiper :0 patchwork]$ fossil pull Server: http://fossil.informatimago.com:8002/patchwork Bytes Cards Artifacts Deltas Sent: 146 2 0 0 Received: 78 2 0 0 Total network traffic: 324 bytes sent, 285 bytes received [pjb&lt; at &gt;kuiper :0 patchwork]$ fossil push Server: http://fossil.informatimago.com:8002/patchwork Bytes Cards Artifacts Deltas Sent: 268 4 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 387 bytes sent, 276 bytes received</pre> Pascal J. Bourguignon 2012-05-07T16:23:53 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9051 <pre> Dear Richard, All, Finally, I've found a bit of time to implement the first draft of the ranges functionality I was posting a couple of months ago (http://www.mail-archive.com/fossil-users-RyYwo1q5J+rPvulMB6uEI2D2FQJk+8+b&lt; at &gt;public.gmane.org/msg07419.html). This is my first contribution to the project so apologize if anything is not that clean and tidy as it should be. From a user point of view the patch changes the way users can do commits. First 'fossil changes' lists changes with additional column indicating the row number, e.g.: 1 EDITED src/checkin.c 2 EDITED src/main.mk 3 EDITED src/makemake.tcl 4 ADDED src/ranges.c 5 EDITED win/Makefile.dmc 6 EDITED win/Makefile.mingw 7 EDITED win/Makefile.msc Then using 'fossil commit --range|-r RANGE_LIST' the user can easily pick only these files they want to check-in, e.g. 'fossil commit -r 1,3-4 -m "added an extension to..."' is equivalent to 'fossil commit -m "added an extension to..." src/checkin.c src/makemake.tcl</pre> Jacek Cała 2012-05-07T14:33:36 http://comments.gmane.org/gmane.comp.version-control.fossil-scm.user/9049 <pre>Hello, Here is a suggestion. When issuing the following error message, write the full pathname of the file on which the error occured. [pjb&lt; at &gt;kuiper :0 src]$ fossil commit -m 'Tested with Lispworks.' generate-application.lisp fossil: SQLITE_FULL: statement aborts at 27: [UPDATE blob SET content=:data WHERE rid=387] fossil: SQL error: database or disk is full If you have recently updated your fossil executable, you might need to run "fossil all rebuild" to bring the repository schemas up to date. [pjb&lt; at &gt;kuiper :0 src]$ (In this case it was /tmp/something). </pre> Pascal J. Bourguignon 2012-05-07T14:13:38 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.version-control.fossil-scm.user