Git Round-Trip Note in ‘Fossil-NG Page’ Compared to ‘Import And Export’ Page
(1) By DB (ABC...) on 2024-06-08 00:43:07 [source]
In general I prefer reading before experimentation before doing.
So I’m thinking these pages/sections are at odds with each other.
Import And Export: Bidirectional Synchronization
Fossil-NG: Round-Trip with Git
It seems the “Round-Trip with Git” section of the “Fossil-NG” wiki page is now obsolete due to “Bidirectional Synchronization” being implemented.
Thank you for clarification.
(2) By Stephan Beal (stephan) on 2024-06-08 10:22:24 in reply to 1 [link] [source]
Fossil-NG
That it's at odds with any given current behavior is to be expected. That page is a scratchpad for ideas, not in any way indicative of current behaviour. From its top paragraph:
Broadly, this document collects ideas that have come up since Fossil was created in 2006 which are difficult enough to build atop the current design that solving them might involve a breakage in compatibility with prior Fossil versions. Much as the hash policy feature forced the change from Fossil 1.x to Fossil 2.0, implementing some of the following ideas might force a similarly epochal shift to "Fossil 3.0" or "Fossil 4.0".
(3) By DB (ABC...) on 2024-06-09 00:34:43 in reply to 2 [link] [source]
I did read that on the Fossil-NG page. I also read, under...
Better Git Integration --> Round-Trip with Git. The part where it says
we’d like a [] command to sync changes to a Git repo back into a Fossil repo, allowing full round-tripping between the two, within the limitations of the various formats.
Which seems outdated compared to what’s on the Import & Export page under Bidirectional Synchronization.
I’m sure a lot of work went into Bidirectional Synchronization. Still going into it. This is not a slam, but a compliment. It seems like a lot of progress has been made since 2019 when the Fossil-NG page was last updated.