Re: [fossil-users] Cannot determine user when using -A
2014-06-06 2:13 GMT+02:00 Philip Bennefall phi...@blastbay.com: fossil user default philip_bennefall And I get the same message again. It says that it cannot determine user. I don't want to use my computer username for the repository, but I can only get it working if I don't pass -A to fossil new. Any hints would be appreciated. Thanks for the report. This is indeed cumersome. Should be fixed in (upcoming) fossil 1.29: fossil-scm.org/index.html/info/4306f0f3d6 Regards, Jan Nijtmans ___ 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 clean --emptydirs ignores file argument
Normally I can do fossil clean subfolder and have the command clean up everything in that subfolder, but appending the --emptydirs flag causes my subdirectory argument to be ignored and fossil clean attempts to work on the entire repository. I'm currently using version [3d49f04587] of fossil. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] TH scripting question
Where do I find the variables and commands Fossil exposes to TH documented? -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. ___ 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] TH scripting question
On Fri, Jun 6, 2014 at 3:47 PM, Michael Richter ttmrich...@gmail.com wrote: Where do I find the variables and commands Fossil exposes to TH documented? Not the answer you want, but... The commands: [stephan@host:~/cvs/fossil/fossil/src]$ grep 'TH command:' *.c th_main.c:** TH command: httpize STRING th_main.c:** TH command: enable_output BOOLEAN th_main.c:** TH command: puts STRING th_main.c:** TH command: html STRING th_main.c:** TH command: wiki STRING th_main.c:** TH command: htmlize STRING th_main.c:** TH command: date th_main.c:** TH command: hascap STRING... th_main.c:** TH command: hasfeature STRING th_main.c:** TH command: tclReady th_main.c:** TH command: anycap STRING th_main.c:** TH command: http ?-asynchronous? ?--? url ?payload? tkt.c:** TH command: append_field FIELD STRING the variables require a bit more investigation to resolve the C-level variables used in most of them: [stephan@host:~/cvs/fossil/fossil/src]$ grep Th_SetVar *.c th.c:** of this structure. Variable values set using the Th_SetVar command th.c:** By default, the Th_SetVar(), Th_UnsetVar() and Th_GetVar() functions th.c:Th_SetVar(interp, (char *)::th_stack_trace, -1, zStack, nStack); th.c:int Th_SetVar( th.c:Th_SetVar(interp, (char *)::th_stack_trace, -1, 0, 0); th_lang.c:Th_SetVar(interp, argv[2], argl[2], zResult, nResult); th_lang.c:Th_SetVar(interp, argv[1], argl[1], argv[2], argl[2]); th_lang.c:Th_SetVar(interp, p-azParam[i], p-anParam[i], zVal, nVal); th_lang.c:Th_SetVar(interp, (const char *)args, -1, zArgs, nArgs); th_main.c:Th_SetVar(interp, zCol, szCol, zVal, szVal); th_main.c:Th_SetVar(g.interp, zName, -1, zValue, strlen(zValue)); th_main.c: Th_SetVar(g.interp, zName, -1, zValue, strlen(zValue)); xfer.c:rc = Th_SetVar(g.interp, uuid, -1, zUuid, -1); -- - 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] TH scripting question
Thus said Stephan Beal on Fri, 06 Jun 2014 18:29:26 +0200: [stephan@host:~/cvs/fossil/fossil/src]$ grep 'TH command:' *.c What about these? $ grep 'TH1 command' th_main.c ** TH1 command: combobox NAME TEXT-LIST NUMLINES ** TH1 command: linecount STRING MAX MIN ** TH1 command: repository ?BOOLEAN? ** TH1 command: utime ** TH1 command: stime ** TH1 command: randhex N ** TH1 command: query SQL CODE ** TH1 command: setting name ** TH1 command: regexp ?-nocase? ?--? exp string Thanks, Andy -- TAI64 timestamp: 400053922b10 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Links within Fossil
I don't think this is currently possible, but I've been wrong before, so let me ask: I know it is possible to link to individual artifacts by ID which displays the source, but is it possible to link to a given line number (range) within a given artifact, perhaps highlighting it in the process? My reason for asking: I've been given a new assignment by my employer to learn / understand some relatively obscure source code written by a former employee. This is proprietary code that can't be shared outside the company, but it is not documented (by which I mean there are comments through the code, but no real design or high level understanding of *why* it does *what* it does). My thoughts on how to handle this task (where code is currently stored in an svn repo and will be migrated in the not too distant future to git) is to take the current code and import it into a fossil repo, then use the wiki / inline documentation features to describe it in detail. Part of what I would like to do in the documentation is link to individual lines or blocks in the individual source files so that the reference is internally complete so that I don't have to keep separate source documentation files in sync. Thanks in advance for your help! -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] autocrlf like in Git?
Does fossil support or has plans to support autocrlf (like Git)? (Text files internally saved always with Linux line endings, but extracted as Win, Linux, Mac line endings depending on the platform FOSSIL runs on)___ 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] autocrlf like in Git?
On Sat, Jun 7, 2014 at 12:15 AM, to...@acm.org wrote: Does fossil support or has plans to support autocrlf (like Git)? (Text files internally saved always with Linux line endings, but extracted as Win, Linux, Mac line endings depending on the platform FOSSIL runs on) Fossil does _no_ conversion of the content because doing so would change its hash compared to the on-disk file. But see: fossil help set ... crnl-globA comma or newline-separated list of GLOB patterns for (versionable) text files in which it is ok to have CR, CR+NL or mixed line endings. Set to * to disable CR+NL checking. Without that, fossil will notice and complain about mixed-mode files. -- - 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] Links within Fossil
On Fri, Jun 6, 2014 at 6:12 PM, Scott Robison sc...@casaderobison.com wrote: I don't think this is currently possible, but I've been wrong before, so let me ask: I know it is possible to link to individual artifacts by ID which displays the source, but is it possible to link to a given line number (range) within a given artifact, perhaps highlighting it in the process? You mean like this: http://www.fossil-scm.org/fossil/artifact/6eb26bb7a6?ln=1755-1759 (Note that the highlighted code is in fact the code that implements the ln= query parameter that does the range highlighting. A kind of semantic recursion.) My reason for asking: I've been given a new assignment by my employer to learn / understand some relatively obscure source code written by a former employee. This is proprietary code that can't be shared outside the company, but it is not documented (by which I mean there are comments through the code, but no real design or high level understanding of *why* it does *what* it does). My thoughts on how to handle this task (where code is currently stored in an svn repo and will be migrated in the not too distant future to git) is to take the current code and import it into a fossil repo, then use the wiki / inline documentation features to describe it in detail. Part of what I would like to do in the documentation is link to individual lines or blocks in the individual source files so that the reference is internally complete so that I don't have to keep separate source documentation files in sync. Thanks in advance for your help! -- Scott Robison ___ 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] TH scripting question
On Fri, Jun 6, 2014 at 10:56 PM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Stephan Beal on Fri, 06 Jun 2014 18:29:26 +0200: [stephan@host:~/cvs/fossil/fossil/src]$ grep 'TH command:' *.c $ grep 'TH1 command' th_main.c Ah, mixed conventions (TH vs TH1). Probably a historical oversight. i grepped against 'TH ...' because the first example i came across used that. -- - 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] Links within Fossil
On Jun 6, 2014 4:20 PM, Richard Hipp d...@sqlite.org wrote: On Fri, Jun 6, 2014 at 6:12 PM, Scott Robison sc...@casaderobison.com wrote: ... is it possible to link to a given line number (range) within a given artifact, perhaps highlighting it in the process? You mean like this: http://www.fossil-scm.org/fossil/artifact/6eb26bb7a6?ln=1755-1759 [Snipped] Thank you so much, that's exactly it! ___ 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] Index (was Re: git-fossil-git does not obtain the same commit hashes.)
I should add that it's not always possible or desirable to test all commits in a bundle that will be pushed together. A goal of breaking up large commits into smaller ones is to make it easier to understand and backport them, but an engineer working on a backport will have to retest anyways. Also, one may want to break up a commit into: code, test, doc updates that go together, in which case the test may not pass for one of those commits by intention. ___ 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] Index (was Re: git-fossil-git does not obtain the same commit hashes.)
On Fri, Jun 6, 2014 at 7:45 PM, Nico Williams n...@cryptonector.com wrote: I should add that it's not always possible or desirable to test all commits in a bundle that will be pushed together. A goal of breaking up large commits into smaller ones is to make it easier to understand and backport them, but an engineer working on a backport will have to retest anyways. Also, one may want to break up a commit into: code, test, doc updates that go together, in which case the test may not pass for one of those commits by intention. This whole discussion speaks to one of the key philosophical differences between Git and Fossil, which is that Fossil strives to record exactly what you did whereas Git strives to record what you should have done. -- 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] TH scripting question
Thus said Stephan Beal on Sat, 07 Jun 2014 00:21:56 +0200: Ah, mixed conventions (TH vs TH1). Probably a historical oversight. i grepped against 'TH ...' because the first example i came across used that. Yes, I actually recently discovered the mixed conventions while testing the ticket change hooks. Andy ___ 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] Index (was Re: git-fossil-git does not obtain the same commit hashes.)
Thus said Nico Williams on Fri, 06 Jun 2014 18:45:13 -0500: I should add that it's not always possible or desirable to test all commits in a bundle that will be pushed together. A goal of breaking up large commits into smaller ones is to make it easier to understand and backport them, but an engineer working on a backport will have to retest anyways. This workflow certainly seems like a lot of time spent playing with the tool and less time working on code. Do Git users typically make such large commits? Why don't they just use branches to separate different lines (as in tracks) of development rather than bundling a bunch of unrelated checkins all at once? Andy -- TAI64 timestamp: 40005392a236 ___ 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] Index (was Re: git-fossil-git does not obtain the same commit hashes.)
On Saturday, June 7, 2014, Andy Bradford amb-sendok-1404710677.ahchkeilcibgninda...@bradfords.org wrote: Thus said Nico Williams on Fri, 06 Jun 2014 18:45:13 -0500: I should add that it's not always possible or desirable to test all commits in a bundle that will be pushed together. A goal of breaking up large commits into smaller ones is to make it easier to understand and backport them, but an engineer working on a backport will have to retest anyways. This workflow certainly seems like a lot of time spent playing with the tool and less time working on code. Do Git users typically make such large commits? Why don't they just use branches to separate different lines (as in tracks) of development rather than bundling a bunch of unrelated checkins all at once? Not git users. Engineers who work on codebases with maintenance releases. For example: Solaris, Windows, ... but also a number of smaller projects, like MIT Kerberos, Heimdal, and so on. When you have a bug that needs to be fixed in older releases, you want to be able to cherry-pick it, and sometimes you don't know this until after you've integrated a fix for it in the main trunk. This is one reason that clean history is appreciated. And when investigating a bug it's also nice to be able to look back through the history and understand what was done (as opposed to how a programmer got there, which is ticket/comment fodder). (For years i worked on codebases where we used Teamware -an ancient, ancient VCS now- and we'd worked out how to implement a rebase-heavy workflow, in a team of thousands. This isn't about git. Git just happens to be the first modern VCS that made this workflow possible with little pain. If i had to use Fossil in such a workflow, I'd do the sorts of things i was used to doing with Teamware, as meantioned earlier in this thread.) The first case is easy to drop: never keep maintenance releases. Mostly that's the right thing to do, especially if in the process you can train your users to stay on the bleeding edge instead of worrying about upgrading with every critical security bugfix. But it's not always possible or easy to do this, or perhaps having older releases on maintenance is part of the vendor's business model. Either way, there's still the matter of clean, comprehensible history -- reasonable people can disagree about this, of course, and precisely because of that there are codebases where the gatekeeprs force a rebase heavy workflow on contributors. I wouldn't, don't, and won't demand that anyone follow such a workflow for any codebase I don't own, and possibly not for codebases I own either (depends). I only want to be able to do it myself easily when working on codebases where i have to or want to. I also want the power of SQL for history, and so on. So I can get this neither from Fossil nor git. Well, so be it. I won't be adding writing a VCS to my bucket list, we each have our priorities, and I wouldn't likely do a very good job of it; at most I will pursue minor extensions (or hooks) to git to get me the query power and recovery semantics I need. I think it best now for me to let this poor dead horse be. Thanks for listening and engaging me on this subject, and my apologies for taking so much of your time (especially since I love SQLite and want to do nothing to slow down your efforts there), Nico -- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
