Overview
Artifact ID: | 93d62a7c57e56a3c6bf614cd96c601e746771e22 |
---|---|
Ticket: | 173e80a4df2d12f239850a28237968cf5713b07e
fossil header/footer/css/ticket pages should be version controlled |
User & Date: | anonymous 2010-05-09 22:06:01 |
Changes
- comment changed to:
Fossil header/footer/css/ticket pages (possibly everything under fossil config) should be version controlled. I understand that it is not desiderable to have them synced by default, but when you DO want to keep them synchronized between several repositories, it would be much simpler if the system automatically knew what is the most current one so the "fossil config sync ..." would do the right thing (currently I must think if I want pull or push, and doing the synchronization automatically is impossible ; also, configuration is transfered even when already identical). Also, ticket [bf536aff75] mentioned that "it would also be nice if these elements were revision controlled, but that is an entirely different ticket" ... I didn't found such ticket so I'm writting it.
- foundin changed to: "11b3f31de959dc5bb81c8d20a4716d6354d2801a"
- private_contact changed to: "bcda72702795946817fd2b0d0b138988a5ad7989"
- severity changed to: "Cosmetic"
- status changed to: "Open"
- title changed to:
fossil header/footer/css/ticket pages should be version controlled
- type changed to: "Feature_Request"