Overview
Artifact ID: | fbf544e5c18fa54d28522193188a01facde0b376 |
---|---|
Ticket: | e29ea5912afe1e97149ad181dc898bc7bbaa6237
Privacy attribution loss due to de/reconstruct ... |
User & Date: | chi 2010-11-18 20:00:53 |
Changes
- comment changed to:
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.
- foundin changed to: "115f3ea60e"
- private_contact changed to: "63f4cb9d6971f7dbdee05412b8546975182b32e4"
- severity changed to: "Severe"
- status changed to: "Open"
- title changed to: "Privacy attribution loss due to de/reconstruct ..."
- type changed to: "Code_Defect"