Re: [fossil-users] a few newbie questions re. wiki and embedded documentation
On Fri, Jan 11, 2013 at 3:34 AM, Miles Fidelman mfidel...@meetinghouse.netwrote: 1. As the documentation indicates, there's no support for working with branching and merging of stand-alone wiki pages, which suggests that .wiki pages within a code tree are more manageable. But. they don't seem to be editable through the web interface - i.e., they are not really wiki-like. Or am I missing something? Is there a way to do real wiki-like things in Fossil (editing, versioning, etc.)? Hello and welcome to Fossil, It sounds like you're missing the proper editing rights. Make sure that you turn on the edit wiki rights in the /admin page. It's correct that wiki pages do not partake in the whole branching/merging/and whatnot - they are maintained linearly. The big advantage of embedded docs vis-a-vis the wiki is that they _do_ partake in branching, which means that a user can point the state of the docs in any given branch. The wiki UI provides no mechanism for fetching/comparing older wiki pages (the JSON API does). 2. The documentation talks about event pages, stating There is a hyperlink under the /Wiki menu that can be used to create new events. And there is a submenu hyperlink on event displays for editing existing events. I don't see these. Again, am I missing something? That's probably due to the missing wiki rights - make sure you have all the necessary rights (note that just having the a (Admin) rights does not imply all other rights like it does in many systems). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Changed tickets report - getting previous values of a field
I'm implementing a Changed Tickets report similar to that in Fossil's ticket system, the main difference is I want to show who made the change. I do this by joining ticket and ticketchg SELECT DISTINCT date(ticket.tkt_mtime), substr(tkt_uuid,1,10) AS '#', status, login, title FROM ticket LEFT OUTER JOIN ticketchng ON ticket.tkt_id = ticketchng.tkt_id ORDER BY ticket.tkt_mtime desc I'd like to do is show the status value for the particular ticket change (rather than the current value) so the report would return something like: DateStatus ModifiedTitle 2013-01-12 Closed Dick 2013-01-12 Tested DickSome task 2013-01-11 DoneHarry Some task 2013-01-10 Started Harry Some task 2013-01-10 OpenDickSome task 2013-01-09 New Tom Some task In this example, assume Tom is an end user, Dick is the tester and Harry is the developer. The above example returned Status Closed for all rows. Can anyone think of a convenient way to achieve the above report? Thanks Steve ___ 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] a few newbie questions re. wiki and embedded documentation
Stephan Beal wrote: On Fri, Jan 11, 2013 at 3:34 AM, Miles Fidelman mfidel...@meetinghouse.net mailto:mfidel...@meetinghouse.net wrote: 1. As the documentation indicates, there's no support for working with branching and merging of stand-alone wiki pages, which suggests that .wiki pages within a code tree are more manageable. But. they don't seem to be editable through the web interface - i.e., they are not really wiki-like. Or am I missing something? Is there a way to do real wiki-like things in Fossil (editing, versioning, etc.)? Hello and welcome to Fossil, It sounds like you're missing the proper editing rights. Make sure that you turn on the edit wiki rights in the /admin page. It's correct that wiki pages do not partake in the whole branching/merging/and whatnot - they are maintained linearly. The big advantage of embedded docs vis-a-vis the wiki is that they _do_ partake in branching, which means that a user can point the state of the docs in any given branch. The wiki UI provides no mechanism for fetching/comparing older wiki pages (the JSON API does). I'm the superuser, and I've explicitly set all the rights. I also seem to be able to create and edit basic wiki pages. Actually my question was, are embedded documentation pages editable through the web gui? 2. The documentation talks about event pages, stating There is a hyperlink under the /Wiki menu that can be used to create new events. And there is a submenu hyperlink on event displays for editing existing events. I don't see these. Again, am I missing something? That's probably due to the missing wiki rights - make sure you have all the necessary rights (note that just having the a (Admin) rights does not imply all other rights like it does in many systems). Again, I do seem to have all rights, and can edit normal wiki pages. I just don't see any distinct hyperlink for events. Hmm... Thanks, Miles -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra ___ 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 few newbie questions re. wiki and embedded documentation
On Thu, Jan 10, 2013 at 9:34 PM, Miles Fidelman mfidel...@meetinghouse.netwrote: 1. As the documentation indicates, there's no support for working with branching and merging of stand-alone wiki pages, which suggests that .wiki pages within a code tree are more manageable. But. they don't seem to be editable through the web interface - i.e., they are not really wiki-like. Or am I missing something? Is there a way to do real wiki-like things in Fossil (editing, versioning, etc.)? Wiki pages are versioned internally, and you can see the complete edit history of a wiki page. See, for example, www.fossil-scm.org/fossil/whistory?name=Cookbook Internally Fossil tracks the ancestry of each wiki edit, so we could construct a DAG of the wiki edit history if we wanted to. But nobody has ever wanted to do that, so nobody has ever bothered to write the queries and the display logic to make it happen. 2. The documentation talks about event pages, stating There is a hyperlink under the /Wiki menu that can be used to create new events. And there is a submenu hyperlink on event displays for editing existing events. I don't see these. Again, am I missing something? The link under the /Wiki menu is Create a new event. You have to have appropriate permissions to see that link. Thanks, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra __**_ fossil-users mailing list fossil-users@lists.fossil-scm.**org fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-usershttp://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] Right way to try something new and save/revert?
On Fri, 11 Jan 2013 13:06:17 +0100 Gilles gilles.gana...@free.fr wrote: Am I correct in understanding that this is the right way to proceed to try some new code, and either save it (whether it works or not, just as a track-record) or discard it? So the right way to experiment and keep tried code for later reference is to save those trials in a branch, distinct from the trunk. But since I've never used branching, I'm not clear about how to see which files have been saved in the branch vs. those in the trunk, You don't need this: a branch diverges from the trunk (in your case), rather than appearing out of the void, so initially it has the same files in the same state the trunk does. Moreover, the Fossil's philosophy is that a new branch is only created when the first commit on it is made, so you start with the trunk, do some changes then do fossil commit --branch crazy_idea and only then your new branch comes into existence. Getting the diff between the starting point of the branch (or an earlier state) is quite rarely needed -- most of the time you're interested in the diff between your work directory (local changes) and its base version (the last recorded commit on the current branch). If you still need the diff between two arbitrary commits, use fossil diff --from A --to B where A and B are either branch/tag names or (possibly abbreviated) hashes of the relevan commits, extracted from the timeline view. You can omit either --from or --to, so, to diff your current checkout to the trunk, just use fossil diff --from trunk and how to check the changes made in a branch to such and such file, Fire up Fossil web UI and click on the links marked patch and diff in the commit view. and how to go back and forth between the trunk and the branch before applying commit. Technically, just by doing `fossil update branchname` as this tries to merge your uncommitted local changes with the branchname you're switching your open checkout to. But, again, what you're asking for is not needed as this is not how VCSes work, so don't do that. Instead, implement your feature on your branch, and if you're OK with it and want it in your mainline (the trunk), go back to the trunk and then *merge* your feature branch into it -- this will bring all the changes implemented on that feature branch and will record that your new commit has two parents (the trunk and the feature branch) so you have understanable history record. ___ 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 few newbie questions re. wiki and embedded documentation
On Fri, Jan 11, 2013 at 2:12 PM, Miles Fidelman
mfidel...@meetinghouse.netwrote:
Actually my question was, are embedded documentation pages editable
through the web gui?
No, unfortunately not. This feature idea has been floated around a few
times, but the commit mechanism really needs a checkout to work with, and
servers don't normally have an associated checkout. On the TODO list for
the JSON API is the ability to check in text files via JSON, which would
allow this feature (as it currently does for wiki pages).
Again, I do seem to have all rights, and can edit normal wiki pages. I
just don't see any distinct hyperlink for events. Hmm...
Under the wiki index page i see:
Create a new event http://fossil-scm.org/index.html/eventedit.
(link = http://fossil-scm.org/index.html/eventedit)
Looking at the permissions page, i see no permission for Events, but
looking at the sources i see...
if( g.perm.NewWiki ){
@ li Create a %z(href(%R/wikinew))new wiki page/a./li
if( g.perm.Write ){
@ li Create a %z(href(%R/eventedit))new event/a./li
}
}
which means: you need both the Create Wiki (letter f) and Write (letter
i for transfer inbound) permissions to see that link. Normally those
perms would be on for the developer pseudo-user and then inherited by any
user with the v (developer) permissions.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
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] Changed tickets report - getting previous values of a field
On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers st...@digitalsmarties.comwrote: I'm implementing a Changed Tickets report similar to that in Fossil's ticket system, the main difference is I want to show who made the change. I do this by joining ticket and ticketchg SELECT DISTINCT date(ticket.tkt_mtime), substr(tkt_uuid,1,10) AS '#', status, login, title FROM ticket LEFT OUTER JOIN ticketchng ON ticket.tkt_id = ticketchng.tkt_id ORDER BY ticket.tkt_mtime desc I'd like to do is show the status value for the particular ticket change (rather than the current value) so the report would return something like: DateStatus ModifiedTitle 2013-01-12 Closed Dick 2013-01-12 Tested DickSome task 2013-01-11 DoneHarry Some task 2013-01-10 Started Harry Some task 2013-01-10 OpenDickSome task 2013-01-09 New Tom Some task In this example, assume Tom is an end user, Dick is the tester and Harry is the developer. The above example returned Status Closed for all rows. Can anyone think of a convenient way to achieve the above report? The status field is coming from the ticket table and thus shows the latest status. To show the latest status at some point in the past, you need a (I think) to first add a status field to your ticketchng table definition. Then modify the query to be something like this (untested): SELECT DISTINCT date(ticket.tkt_mtime), substr(tkt_uuid,1,10) AS '#', (SELECT status FROM tkt_chng AS chng2 WHERE chng2.tkt_id = ckc1.tkt_id AND chng2.tkt_time = chng1.tkt_time AND chng2.status IS NOT NULL ORDER BY chng2.tkt_time DESC LIMIT 1), login, title FROM ticket AS tkt1 LEFT OUTER JOIN ticketchng AS chng1 ON tkt1.tkt_id = chng1.tkt_id ORDER BY tkt1.tkt_mtime desc Thanks Steve ___ 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] Changed tickets report - getting previous values of a field
On Fri, Jan 11, 2013 at 8:37 AM, Richard Hipp d...@sqlite.org wrote: The status field is coming from the ticket table and thus shows the latest status. To show the latest status at some point in the past, you need a (I think) to first add a status field to your ticketchng table definition. Then modify the query to be something like this (untested): SELECT DISTINCT date(ticket.tkt_mtime), substr(tkt_uuid,1,10) AS '#', (SELECT status FROM tkt_chng AS chng2 WHERE chng2.tkt_id = ckc1.tkt_id AND chng2.tkt_time = chng1.tkt_time AND chng2.status IS NOT NULL ORDER BY chng2.tkt_time DESC LIMIT 1), login, title FROM ticket AS tkt1 LEFT OUTER JOIN ticketchng AS chng1 ON tkt1.tkt_id = chng1.tkt_id ORDER BY tkt1.tkt_mtime desc Later today, I'll try to find time to enhance Fossil so that you can accomplish the above merely by creating a status column in the TICKETCHNG table and omitting the subquery. -- 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] Right way to try something new and save/revert?
On Fri, 11 Jan 2013 17:19:40 +0400, Konstantin Khomoutov flatw...@users.sourceforge.net wrote: and how to check the changes made in a branch to such and such file, Fire up Fossil web UI and click on the links marked patch and diff in the commit view. This is really what I want to do: Being able to see all the things I tried on a file in the branch. Most of the time, I want to keep track of things I tried just in case instead of just forgetting about them with fossil revert. Can this be done with calling a Windows application, either a regular editor or a differ instead of the Fossil web server? I prefer working with dedicated applications. Technically, just by doing `fossil update branchname` as this tries to merge your uncommitted local changes with the branchname you're switching your open checkout to. I was under the impression that update simply told Fossil than any subsequent commit should be done on that thread/trunk. Good to know that update will perform a merge, so it has consequences. ___ 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] Right way to try something new and save/revert?
On Fri, 11 Jan 2013 17:11:44 +0100, Gilles gilles.gana...@free.fr wrote: This is really what I want to do: Being able to see all the things I tried on a file in the branch. Most of the time, I want to keep track of things I tried just in case instead of just forgetting about them with fossil revert. What I'm driving at: 1. Keep tried but NOK algos in a branch called eg. experimental 2. Find a simple way to locate old algo's I know I tried before by searching Fossil, regardless of which branch they are (trunk or experimental). I know Fossil doesn't support grep yet, but I find it useful to being able to just commit code and know for sure that I can find anything in the repo. ___ 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] Right way to try something new and save/revert?
On Fri, 11 Jan 2013 17:11:44 +0100 Gilles gilles.gana...@free.fr wrote: Fire up Fossil web UI and click on the links marked patch and diff in the commit view. This is really what I want to do: Being able to see all the things I tried on a file in the branch. Most of the time, I want to keep track of things I tried just in case instead of just forgetting about them with fossil revert. `fossil revert` is there for special whoops! cases, not for organising some sort of serious workflow around it. Can this be done with calling a Windows application, either a regular editor or a differ instead of the Fossil web server? I prefer working with dedicated applications. There's no official GUI front-end for fossil, but there are several attempts at creating such a thing. Google mail archives for it, using something like http://www.google.com/search?q=GUI+site%3Amail-archive.com%2Ffossil-users%40lists.fossil-scm.org to get the relevant discussions/links. Using GUI diffing programs was also discussed several times. Technically, just by doing `fossil update branchname` as this tries to merge your uncommitted local changes with the branchname you're switching your open checkout to. I was under the impression that update simply told Fossil than any subsequent commit should be done on that thread/trunk. Good to know that update will perform a merge, so it has consequences. The logic behind `fossil update` is like follows. Your work tree (working directory, current checkout and whatever else it's being named) is always based on some state stored in the repository (except for the special case when the repository has no commits at all yet). So the main task of `fossil update` is to bring your work tree to the state held by the commit you supplied to this command (directly, or via the name of a branch or a tag). Of course, when fossil does this, it has to be non-destructive: it should not stomp over untracked files (files present in the work tree but not being managed by fossil) and it should preserve your local modifications, if any, which it does by merging. After than, when you modify something and record a commit, that new commit inherits certain properties from the base commit of your work tree, and if that commit is on a branch, then your new commit will be on that same branch, too. ___ 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] Right way to try something new and save/revert?
On Fri, 11 Jan 2013 17:25:24 +0100 Gilles gilles.gana...@free.fr wrote: [...] What I'm driving at: 1. Keep tried but NOK algos in a branch called eg. experimental 2. Find a simple way to locate old algo's I know I tried before by searching Fossil, regardless of which branch they are (trunk or experimental). I know Fossil doesn't support grep yet, but I find it useful to being able to just commit code and know for sure that I can find anything in the repo. You could go for documenting your experiments then. First of all, you can assign arbitrary tags to the tip commits of your experimental lines of history. A tag view is there to select the one you need. Another easy possibilty is the wiki: you can refer to any commit using its SHA-1 name in square brackets, so you can create a page titled, say, experiments and roll something like this: h2My experiments/h2 * [44c9e93a9187a07340da8b2984b2118990637d5a|A crazy idea] * [8a428d5c2a0097418170509ab03faed0a335f796|Using bars to style foos] ... where you get those SHA-1 commit names from the commit views. The end result is that you have a nice-looking list of your experimental lines of history, decorated by arbitrary comments. ___ 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 Fri, 11 Jan 2013 11:36:10 +0100 Remigiusz Modrzejewski l...@maxnet.org.pl wrote: 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. Yes, that's possible. It's not a very satisfying solution though as I now have to have extra infrastructure running and have to make lots of frequent redundant pulls/pushes as opposed to only doing them when they're actually needed. M ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] problem with selecting timeline entries for diffing in the GUI
my question regards the (very useful!) functionality of selecting (clicking) two timeline entries in the web GUI to the repo for diffing. this works alright for me with a certain (remote) repository. it does +not+ work for the local copy of that repo or any other local repo (under URL http://localhost:8080/timeline), i.e. the first click on a timeline square remains ineffective (no red highlight) as does the second (no diff appearing). what am I missing? -- 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] problem with selecting timeline entries for diffing in the GUI
On Fri, Jan 11, 2013 at 12:45 PM, j. van den hoff veedeeh...@googlemail.com wrote: my question regards the (very useful!) functionality of selecting (clicking) two timeline entries in the web GUI to the repo for diffing. this works alright for me with a certain (remote) repository. it does +not+ work for the local copy of that repo or any other local repo (under URL http://localhost:8080/timeline**), i.e. the first click on a timeline square remains ineffective (no red highlight) as does the second (no diff appearing). what am I missing? My guess: you are running an older version of Fossil locally that does not support that feature. The feature was added recently and has not yet appeared in a precompiled binary. -- Using Opera's revolutionary email client: http://www.opera.com/mail/ __**_ fossil-users mailing list fossil-users@lists.fossil-scm.**org fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-usershttp://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] Changed tickets report - getting previous values of a field
On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers st...@digitalsmarties.comwrote: I'm implementing a Changed Tickets report similar to that in Fossil's ticket system, the main difference is I want to show who made the change. I do this by joining ticket and ticketchg How is the /timeline?y=t page is insufficient for this? SELECT DISTINCT date(ticket.tkt_mtime), substr(tkt_uuid,1,10) AS '#', status, login, title FROM ticket LEFT OUTER JOIN ticketchng ON ticket.tkt_id = ticketchng.tkt_id ORDER BY ticket.tkt_mtime desc I'd like to do is show the status value for the particular ticket change (rather than the current value) so the report would return something like: DateStatus ModifiedTitle 2013-01-12 Closed Dick 2013-01-12 Tested DickSome task 2013-01-11 DoneHarry Some task 2013-01-10 Started Harry Some task 2013-01-10 OpenDickSome task 2013-01-09 New Tom Some task In this example, assume Tom is an end user, Dick is the tester and Harry is the developer. The above example returned Status Closed for all rows. Can anyone think of a convenient way to achieve the above report? Thanks Steve ___ 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] problem with selecting timeline entries for diffing in the GUI
On Fri, 11 Jan 2013 18:57:34 +0100, Richard Hipp d...@sqlite.org wrote: On Fri, Jan 11, 2013 at 12:45 PM, j. van den hoff veedeeh...@googlemail.com wrote: my question regards the (very useful!) functionality of selecting (clicking) two timeline entries in the web GUI to the repo for diffing. this works alright for me with a certain (remote) repository. it does +not+ work for the local copy of that repo or any other local repo (under URL http://localhost:8080/timeline**), i.e. the first click on a timeline square remains ineffective (no red highlight) as does the second (no diff appearing). what am I missing? My guess: you are running an older version of Fossil locally that does not support that feature. The feature was added recently and has not yet appeared in a precompiled binary. ah, yes of course. thank you for clarifying. -- Using Opera's revolutionary email client: http://www.opera.com/mail/ __**_ fossil-users mailing list fossil-users@lists.fossil-scm.**org fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-usershttp://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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] `fossil info' feature request (a.k.a. wish)
On Thu, 10 Jan 2013 13:51:51 +0100, Stephan Beal sgb...@googlemail.com wrote: On Thu, Jan 10, 2013 at 1:35 PM, Stephan Beal sgb...@googlemail.com wrote: i'll sign up for adding that - i would be able to do this on Sunday. i would add it to the status command because we have that info in the /stat page already (and in fossil json stat -full). Don't tell my boss this, but... http://fossil-scm.org/index.html/info/acea7010b8 i added the output to info instead of status because that seemed to be the better place for it (status reports local change status). I just tested it and I stumbled: the reported checkin count is _approximately_ (order of magnitude...) correct but does _not_ match the actual number of checkins (nor the number of file checkins only). e.g. for the fossil repo itself (as of today at e4ca677a6c), `fossil info' reports checkin-count: 4845 however, I do see a total (files+wiki+ticket) of 8799 checkins and fossil time -t ci -n 1|grep ^[0-9]|wc -l yields 4009. so what is `checkin-count' actually reporting?? what I currently would find most useful is to see the total number (8799 in the example), but maybe instead a more detailed statistics (file ci: xxx; wiki ci: , bug ci: ) is also of interest. thanks j. ps: in the long run I would really like to have fossil report chronological local revision numbers in the timeline (cumulative across files, wiki, tickets) in addition to the hashes (plus abilitity to use themas alias in all commands currently requesting specification of hashes). that would be at least nice to have in order to facilitate interaction with fossil, notably when using commands like `diff', `cat', etc. [stephan@host:~/cvs/fossil/fossil]$ f info project-name: Fossil ... checkin-count: 4840 -- 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] `fossil info' feature request (a.k.a. wish)
On Fri, Jan 11, 2013 at 9:04 PM, j. v. d. hoff veedeeh...@googlemail.comwrote: checkin-count: 4845 however, I do see a total (files+wiki+ticket) of 8799 checkins and fossil time -t ci -n 1|grep ^[0-9]|wc -l yields 4009. so what is `checkin-count' actually reporting?? Whatever is shown in the /stat page. i re-used the same query as that code uses, but i'm not familiar enough with the semantics of the mlink table to say with absolutely certainty what it's counting (it seems to me to be the number of normal (file-level) commits). what I currently would find most useful is to see the total number (8799 in the example), but maybe instead a more detailed statistics (file ci: xxx; wiki ci: , bug ci: ) is also of interest. i'll add wiki/ticket commit/change counts to the todo list for Sunday. (i'm about to leave town until then.) ps: in the long run I would really like to have fossil report chronological local revision numbers in the timeline (cumulative across files, wiki, tickets) in addition to the hashes (plus abilitity to use themas alias in all commands currently requesting specification of hashes). that would be at least nice to have in order to facilitate interaction with fossil, notably when using commands like `diff', `cat', etc. @DRH: perhaps we could abuse the rid for this purpose? AFAIK those have never been published as stable/external numbers? They wouldn't be strictly sequential (there'd be gaps in, e.g., the list of commit numbers b/c the blob table holds all types of artifacts), but this sounds like it might not be all that invasive. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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 few newbie questions re. wiki and embedded documentation
Stephan Beal wrote: On Fri, Jan 11, 2013 at 2:12 PM, Miles Fidelman mfidel...@meetinghouse.net mailto:mfidel...@meetinghouse.net wrote: Actually my question was, are embedded documentation pages editable through the web gui? No, unfortunately not. This feature idea has been floated around a few times, but the commit mechanism really needs a checkout to work with, and servers don't normally have an associated checkout. On the TODO list for the JSON API is the ability to check in text files via JSON, which would allow this feature (as it currently does for wiki pages). Ahh... that's a shame. I guess I stick with the basic wiki pages. Again, I do seem to have all rights, and can edit normal wiki pages. I just don't see any distinct hyperlink for events. Hmm... Under the wiki index page i see: Create a new event http://fossil-scm.org/index.html/eventedit. Big oops on my part. I installed the Debian Squeeze package, which seems to be ancient (well 2010). I installed the latest version for source and there it was. Of course, now that I look at it, it's somewhat overstated to call events a distributed blog - the pages are somewhat hidden, no commenting, no subscription mechanism. Ahh... Fossil is so close to doing it all, but Sigh.. Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra ___ 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] Changed tickets report - getting previous values of a field
On 11/01/2013, at 9:44 PM, Richard Hipp d...@sqlite.org wrote: The status field is coming from the ticket table and thus shows the latest status. To show the latest status at some point in the past, you need a (I think) to first add a status field to your ticketchng table definition. Then modify the query to be something like this (untested): SELECT DISTINCT date(ticket.tkt_mtime), substr(tkt_uuid,1,10) AS '#', (SELECT status FROM tkt_chng AS chng2 WHERE chng2.tkt_id = ckc1.tkt_id AND chng2.tkt_time = chng1.tkt_time AND chng2.status IS NOT NULL ORDER BY chng2.tkt_time DESC LIMIT 1), login, title FROM ticket AS tkt1 LEFT OUTER JOIN ticketchng AS chng1 ON tkt1.tkt_id = chng1.tkt_id ORDER BY tkt1.tkt_mtime desc Excellent, thx. That shows me a way forward. Later today, I'll try to find time to enhance Fossil so that you can accomplish the above merely by creating a status column in the TICKETCHNG table and omitting the subquery. Even better. On Fri, Jan 11, 2013 at 3:07 AM, Steve Landers st...@digitalsmarties.com wrote: I'm implementing a Changed Tickets report similar to that in Fossil's ticket system, the main difference is I want to show who made the change. I do this by joining ticket and ticketchg How is the /timeline?y=t page is insufficient for this? It's not tabular and not easily configurable (color, number of entries or recent entries by time, order/sorting/format of columns, etc). Plus, I've added sortable columns via javascript. So, the information is there but not as accessible. Thanks again Richard. As always, much appreciated. Steve ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
