History Of Ticket 057b6d23da
Not logged in
HomeFilesLeavesTimelineBranchesTagsTicketsWikiLogin
Status Timeline
Ticket change [477b2ac5e7] (rid 5551) by anonymous on 2009-11-03 20:02:15:
  1. Appended to comment:

    anonymous added on 2009-11-03 20:02:15:
    You could certainly shrink the window though by comparing the version at the start with the version just before the actual commit (once notes, gpg, etc. done.)

Ticket change [49cccba2f7] (rid 5514) by drh on 2009-10-31 13:17:04:
  1. Appended to comment:

    drh added on 2009-10-31 13:17:04:
    I don't think this is a bug. This is simply the way distributed version control systems work. The fork is easily resolved using a subsequent merge. Indeed, with DVCSes other than Fossil, that's what you would have to do all the time anyway. Fossil provides auto-sync which helps to reduce forks, but I don't think it can eliminate them 100%.

  2. Change resolution to "Not_A_Bug"
  3. Change status to "Closed"
Ticket change [5b3a3cc4f2] (rid 5480) by anonymous on 2009-10-21 18:02:56:
  1. Change comment to "An accidental fork was created in the SQLite project today with both users having autosync enabled and working online. It is suspected that both users started their commits at about the same time, but because of the different times taken to complete the check-in (editing comments, etc.), a fork was created."
  2. Change foundin to "79be9028eb"
  3. Change private_contact to "6e2163462fb7f11c3a9d62f715eac2bff3e678e7"
  4. Change severity to "Minor"
  5. Change status to "Open"
  6. Change title to "possible fork with autosync enabled"
  7. Change type to "Code_Defect"

Fossil version [c0211010a1] 2009-12-13 01:31:36