1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
1
2
3
4
5
6
7
8
9
10
11
12
13
|
-
|
An informal list of FIXMEs which don't warrant full tickets...
This is not *intended* to be a list of long-lived fixme's, but more of a scratchpad for things which come up spontaneously and shouldn't be forgotten.
In no particular order...
|
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
+
+
+
+
+
+
+
+
+
+
+
+
+
|
This list is for potential backports from fossil which should be investigated more closely to determine whether they need to be adapted for use in this library:
- Improved diff output with `--from BRANCH` when it names a branch which was just merged into the local checkout: <s>[](fossil:edb3a3a06369c1e7bd29)</s>
[](fossil:960c9e8bd69531eb)
# f-apps-specific
## f-ci
When checking whether a parent check-in is newer than the currently-being-made checkin, amendment tags which modify the parent's timestamp are not taken into account. For example:
>
```
$ f-ci -m "Update autosetup from upstream trunk."
...
f-ci: ERROR #104 (FSL_RC_RANGE): Parent checkin is more recent (2025-04-03T23:18:00) than this checkin (2025-04-03T22:48:02). Use --allow-older to permit this.
```
In that case, a VM's skewed clock caused the parent checkin to be way off, requiring a manual `--date-override` on that checkin. Later it was determined that the in-my-head math for the timezone adjustment was done in the wrong direction from UTC, at which point a tag was applied to update the timestamp. Shortly later, making the above checkin was looking at the parent's original timestamp, not its amended time.
## f-vdiff
#### Recognize Renames
f-vdiff, when comparing to the local checkout, needs to be able to recognize renames. Case in point:
```
|