Fossil

Search
Login
  1. Document: Web-Page Examples
    ... src/doc.c. ? (Hint: In the pages above, click the graph nodes for any two check-ins or files to see a diff.) ? (Example) ? Full-text search for "interesting pages". (Example) ? All files for a ... (2021-01-03)

  2. Document: Use of JavaScript in Fossil
    ... rather than forcing a page-reload via a button click. Workaround: Manually edit the URL to give the “ln” query parameter per the /file docs. Potential Better Workaround: Someone sufficiently interested could provide a patch ... (2021-01-21)

  3. Ticket: auto-discovery of a repository from a webpage (2013-01-25 18:52:55)
    type: Code_Defect | status: Fixed | foundin: [12a79e5b93] | resolution: Fixed | comment: Now the commit page (info) shows an "ancestors" link, but if one parent has lots of commits done before the other parent, it's hard to find the link to that 2nd parent. Now the only easy way I could find is to look at the manifest for the parents. I think the best would be the ancestors page to have a way to show at least all the parents. <hr /><i>anonymous claiming to be Joerg Sonnenberger added on 2010-11-23 14:16:20:</i><br /> (Title updated as this is about commits, not branches) |

  4. Wiki: checkin/ef5424b683ad2830bfb111ea5756e00e3b8be5df5692ec95d28f1d851170c7c5
    ... used the name of the file where those pages are collected as the common type for pages served from that file. e.g. "cache" Other points of interest: The implementation of proc styleFooter in TH1 ... (2020-11-05)

  5. Ticket: make wiki (code?, bugs?) searchable (2015-02-14 15:24:22)
    ... branch to make it private after the fact (or remove privacy afterwards) would be a nice add-ontype: Code_Defect | status: Fixed | severity: Severe | foundin: 115f3ea60e | resolution: Fixed | comment: As I also use Git in our company to communicate with Subversion used at work, I liked the fact, that I can work locally, change the commit and comments and if all is finish, I can checkin to the central repository. Now I intent to use Fossil's privat branches the same way. I intend to make my own checkins locally and if I am finished I send all with a big checkin to my central repository by merging the private branch into a non-private one to get it pushed later on. So far so good. As I investigated the possibility to implement a feature in Fossil to get private branches pushed as well (but not synced or pulled) for backup purposes, I stumbled over the fact, that private branches lose its privacy attribution, if I deconstruct (with following reconstruction) a repository. What makes it worse is, that if I look at the reconstructed repository the private branch looks exactly like at the original repository. I cannot determine, it is not private any longer. Therefore it will be cloned and synced as well ... I will attach a small shell script to show the bug ... Best regards, chi. <hr /><i>anonymous claiming to be Joerg Sonnenberger added on 2010-11-18 22:47:06:</i><br /> This is partially by design. Private / public is not a property in the manifest and can't survive a deconstruct as such. It would be useful for this kind of situation to be able to edit the property afterward, but it seems like the normal edit can't do that ATM? <hr /><i>chi added on 2010-11-19 12:00:41:</i><br /> You mean "by design"? I thought, it was by accident ... I feel the behavior not correct. I mean reconstructing a repository should result in the same repository afterwards. Otherwise it would be a destroying operation. Of course, your idea to edit a branch to make it private after the fact (or remove privacy afterwards) would be a nice add-on too. But for reconstruction, I feel the privacy should survive. If we could have some card within a manifest to mark privacy, this could also be used to allow to push private branches to other repositories as well. Then we could use the push mechanism to allow incremental backup of Fossil repositories to another server without copying the whole repository all the time again and again ... <hr /><i>anonymous claiming to be Joerg Sonnenberger added on 2010-11-19 12:10:46:</i><br /> deconstruct / reconstruct only preserve persistent data, e.g. the manifests and linked entries. The "private" flag is (intentionally) not persistent as it would prevent publishing the changes later. |

  6. Check-in [d7dc41586fc0d785] on 2013-10-19 06:47:25
    ... The /vdiff page can have a lot of files to diff depending on which version are selected, so the capability to show only list of files that change is very convenient to spot interesting files ...

  7. Document: Fossil Versus Git
    ... but that's most likely due to lack of interest rather than inherent difficulties in doing the port ... other history rewriting mechanism listed on the Git documentation page linked above. There is no rebase in Fossil ... (2021-01-21)

  8. Document: JSON API: Hacker's Guide
    ... documented and demonstrated on this page: https://fossil.wanderinghorse.net/wikis/cson/?page=TipsAndTricks In short, after creating ... Results to JSON This section will only be of interest to those wanting to work on the Fossil ... (2020-11-25)

  9. Ticket: Cyrillic symbols does not display correctly (2010-02-16 20:03:28)
    ... resolution: Fixed | comment: The da39a3ee5e artifact (all empty files) shown in single long line - http://www.fossil-scmtype: Code_Defect | status: Fixed | severity: Cosmetic | foundin: f969b6cdde | resolution: Fixed | comment: The da39a3ee5e artifact (all empty files) shown in single long line - http://www.fossil-scm.org/index.html/artifact/da39a3ee5e but should be separate line for each file (insert BR before 'Also file'). <hr /><i>dmitry added on 2011-09-08 18:47:47 UTC:</i><br /> Fixed in [49402fc722]. |

  10. Document: JSON API Introduction
    ... files) is not an initial goal, but "might be interesting" once the overall infrastructure is in place and ... end. This approach also allows clients to serve wiki pages in a format of their choice - since all ... (2020-12-22)

  11. Document: The Annotate Algorithm
    ... praise commands, and the /annotate, /blame, and /praise web pages are all used to show the most recent ... changes by modifications to step 3. Step 2 is interesting in that it is implemented using a recursive ... (2020-11-25)

  12. Document: Fossil Performance
    ... In Fossil, every version of every file, every wiki page, every change to every ticket, and every check ... kibibytes. Analysis And Supplemental Data Perhaps the two most interesting data points in the above table are SQLite ... (2020-11-25)

  13. Document: JSON API: General Conventions
    ... spacing, and adding them to this interface might be interesting at some point. e.g. whether or not ... not allowed. e.g. trying to create a wiki page or user which already exists. FIXME? Consolidate this ... (2020-11-25)

  14. Check-in [893bf2a146be9e9c] on 2020-09-15 07:51:19
    Consolidate pikchrshow page/pikchr command use of pikchr()/th1 into a shared routine. Though /pikchrshow does not currently allow th1-processed scripts, it might be interesting to enable for users with edit/checkin (or admin ...

  15. Ticket: fossil rollback (2015-02-17 00:55:53)
    ... in one go.<br> At that moment I get fossil web interface, where I see freshly created repo.<br> If I go there to the timeline menu, I see there one enty title "1 most ...

  16. Ticket: nowiki tag limitations (2014-05-31 18:53:58)
    ... supposed to do). i use multiple NOWIKI tags in pages very often with no problems. |login: anonymous | username ... block-level constructs which the parser takes a substantial interest in. i do not have a definitive list ...

  17. Ticket: Windows 7: "fossil ui" and "fossil server" fail (2012-09-24 11:42:42)
    type: Code_Defect | status: Fixed | severity: Minor | foundin: 1.30 | resolution: Fixed | login: nobody | icomment: Minor/cosmetic issue. (I've never really noticed prior discovering it in the new sitemap.) Live example on [http://fossil-scm.org/index.html/attachlist] :) The /attachview and /attachdownload links in attachlist are absolute paths. Therefore they'll generate 404s on most public setups. Another simple %R prefix in attach.c seems to work. @ <br><a href="%R/attachview?%s(zUrlTail)">%h(zFilename)</a> @ [<a href="%R/attachdownload/%t(zFilename)?%s(zUrlTail)">download</a>]<br /> |login: drh | icomment: Check-in [0438d06635892890f39f78995799539d25607e23] |type: Code_Defect | status: Fixed | severity: Minor | foundin: 1.30 | resolution: Fixed | login: nobody | icomment: Minor/cosmetic issue. (I've never really noticed prior discovering it in the new sitemap.) Live example on [http://fossil-scm.org/index.html/attachlist] :) The /attachview and /attachdownload links in attachlist are absolute paths. Therefore they'll generate 404s on most public setups. Another simple %R prefix in attach.c seems to work. @ <br><a href="%R/attachview?%s(zUrlTail)">%h(zFilename)</a> @ [<a href="%R/attachdownload/%t(zFilename)?%s(zUrlTail)">download</a>]<br /> |login: drh | icomment: Check-in [0438d06635892890f39f78995799539d25607e23] |

  18. Ticket: 'annotate' misses changes. (2011-10-19 20:16:18)
    type: Code_Defect | status: Open | severity: Minor | comment: <verbatim> $ mkdir test $ cd test $ fossil init test project-id: 5545d1358dffb32424958343acc90220c6a03ec7 server-id: 6ba5d397e66d52d97fd97befc18ccbff8e19b37a admin-user: joerg (initial password is "484064") $ fossil sqlite3 test fossil: use --repository or -R to specify the repository database $ fossil sqlite3 -R test test2 SQLite version 3.7.4 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> vacuum; sqlite> .quit $ ls test test2 </verbatim> The -R should not be required and either not be accepted or complain if given both a repository as positional argument and via -R. It would be nice if it accepted SQL commands as command line parameter like the standalone sqlite3 command. Handling EOF as implicit ; would be another minor improvement. | type: Code_Defect | status: Open | severity: Minor | comment: <verbatim> $ mkdir test $ cd test $ fossil init test project-id: 5545d1358dffb32424958343acc90220c6a03ec7 server-id: 6ba5d397e66d52d97fd97befc18ccbff8e19b37a admin-user: joerg (initial password is "484064") $ fossil sqlite3 test fossil: use --repository or -R to specify the repository database $ fossil sqlite3 -R test test2 SQLite version 3.7.4 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> vacuum; sqlite> .quit $ ls test test2 </verbatim> The -R should not be required and either not be accepted or complain if given both a repository as positional argument and via -R. It would be nice if it accepted SQL commands as command line parameter like the standalone sqlite3 command. Handling EOF as implicit ; would be another minor improvement. |

  19. Ticket: Color picker (edit check-in properties) (2011-09-08 21:14:02)
    ... name shows up <hr><i>kejoki added on 2008-11-25 04:31:56:</i><br> Oh well. | type: Incident | status: Closed | resolution: Duplicate | comment: testing to see if initial user name shows up <hr><i>kejoki added on 2008-11-25 04:31:56:</i><br> Oh well. |

  20. Ticket: Post-push patch (2010-10-19 08:03:24)
    type: Code_Defect | status: Fixed | severity: Minor | foundin: ceab53718f | resolution: Fixed | comment: When starting a new repository the index page (Admin -> Configuration) shows /home initially this redirects to /index. If you change this string to something else and then back to '/home' browsers report a redirect loop. What happens: Fossil stores the index page in table 'config' with key 'index-page'. Initially this record does not exist, and you get redirected to /index. Modifying the configuration overrides the default behavior. It is impossible however to get the original behavior back. The problem is that setting the string back to '/home' keeps the record in 'config', which causes the problem. Running "delete from config where name = 'index-page';" restores the original behavior and gets rid of the redirect loop. Suggestion: remove the record when the admin sets the index page to '/home'. | type: Code_Defect | status: Fixed | severity: Minor | foundin: ceab53718f | resolution: Fixed | comment: When starting a new repository the index page (Admin -> Configuration) shows /home initially this redirects to /index. If you change this string to something else and then back to '/home' browsers report a redirect loop. What happens: Fossil stores the index page in table 'config' with key 'index-page'. Initially this record does not exist, and you get redirected to /index. Modifying the configuration overrides the default behavior. It is impossible however to get the original behavior back. The problem is that setting the string back to '/home' keeps the record in 'config', which causes the problem. Running "delete from config where name = 'index-page';" restores the original behavior and gets rid of the redirect loop. Suggestion: remove the record when the admin sets the index page to '/home'. |

  21. Ticket: Attachment Download Link (2010-09-27 08:51:10)
    ... timeline, and the graph stops earlier than the end of the page. <hr /><i>drh added on 2011type: Code_Defect | status: Closed | foundin: [cea065c7f2] 2011-04-18 | resolution: Unable_To_Reproduce | comment: I was looking at the '200 entries' 'only checkins' of the current fossil-scm.org timeline, and the graph stops earlier than the end of the page. <hr /><i>drh added on 2011-04-19 18:49:32 UTC:</i><br /> I tried this on Firefox, Chrome, Safari, Opera, and IE. Works fine on all browsers as far as I can see. <hr /><i>viriketo added on 2011-04-19 19:36:14 UTC:</i><br /> Really? Have you really checked that '200 entries' and 'checkins only' are both enabled? I'm using firefox 3.6.15 on linux here. <hr /><i>viriketo added on 2011-04-20 07:36:06 UTC:</i><br /> On firefox 3.6.16 I don't see it anymore. |

  22. Ticket: default ticket schema does not include "submitted by" (2010-02-18 17:38:05)
    ... on 2009-10-07 17:57:12:</i><br> interesting - somehow the timeline knows who submitted a given ... submitted_by" field, which is autopopulated. On the 'new ticket' page, the email should be automatically filled in from ...

  23. Ticket: Message "killed" opening large repository (2010-01-20 16:56:19)
    type: Feature_Request | status: Closed | severity: Important | resolution: Duplicate | comment: i'm using the fossil checkout dir, as my application directory too, i create a couple of sub dirs for app data, this works fine, except of course, when your looking at fossil extras. Actually, another option would be fossil extras --ignore dir1,dir2 that would satisfy my issues <hr><i>jeremy_c added on 2009-12-31 04:29:49:</i><br> Basically a duplicate of [4e8410bfd6] | type: Feature_Request | status: Closed | severity: Important | resolution: Duplicate | comment: i'm using the fossil checkout dir, as my application directory too, i create a couple of sub dirs for app data, this works fine, except of course, when your looking at fossil extras. Actually, another option would be fossil extras --ignore dir1,dir2 that would satisfy my issues <hr><i>jeremy_c added on 2009-12-31 04:29:49:</i><br> Basically a duplicate of [4e8410bfd6] |