Fossil

Timeline
Login

Timeline

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

6 most recent check-ins by user mark

2023-08-08
11:26
Disable rc_reload in the example rc(8) script in the OpenBSD docs. Reloading is unsupported by Fossil such that 'rcctl reload fossil' kills the process. Suggested by James Cook: 73520532dd. (check-in: f0e1d0c9 user: mark tags: trunk)
2023-07-09
03:13
Show default value of settings that have a default in 'fossil help SETTING' output. These values are otherwise only documented in the source code. ok stephan, danield (check-in: 1e1a319e user: mark tags: trunk)
2023-07-07
11:55
JSON API: mention 'priorName' of renamed files in status report

As discussed with Stephan in /chat. File objects in the renamed case possess a 'priorName' property in addition to the 'name' reported in all cases. (check-in: f8d6e8c1 user: mark tags: trunk)

2023-07-01
16:06
give 'json status' the same rename treatment as recent status work

As reported by larrybr on the forum: 9e9778f2e6, 'fossil json status' reports renamed _and_ edited files as only renamed. This change reports such cases as both edited and renamed, and displays the filename prior to being renamed as well as the renamed path. We now also update the vfile table before generating the status report to ensure the current checkout state is reported. (check-in: 771e592b user: mark tags: trunk)

2023-06-28
12:40
report renamed state when file is both edited and renamed

In `fossil {changes,status}` and the commit description shown in the editor with `fossil commit`, show the original and renamed path annotation if the file has been renamed and edited. Prior to this, the file was only reported as edited, which can be confusing. Reported by James Cook 5a4c530e6b. Discussed with stephan@ and danield@, plus some forum members. While here, make sure we honour the relative-paths setting/option when displaying the original pathname in the renamed case. (check-in: ca9d0ddf user: mark tags: trunk)

2023-06-22
13:49
enable importing multiple git repos into one fsl repo

This fixes an issue reported by James Cook in d162b6e2dc. Previously, we assumed the fx_git table does not exist when creating a new import, thus the previously untested use case of importing multiple new (read: not incremental) git repos into the same fossil repo failed at this assumption. While here, document the persistent nature of attributions in the import cmd help text; previously, this was only in the online docs: /doc/trunk/www/inout.wiki (check-in: 47fb3ddc user: mark tags: trunk)