1. 16 Aug, 2012 4 commits
  2. 09 Aug, 2012 6 commits
  3. 25 Jul, 2012 5 commits
  4. 19 Jul, 2012 1 commit
    • Sriram Karra's avatar
      Do not continue if bbdb records cannot be parsed · 90a6a9b6
      Sriram Karra authored
      During a sync it causes problems if we try to ignore bbdb record
      parse errors. This is particularly dangerous with the contact
      delete syncing, as the records that could not be parsed are treated
      as deletions and removed from the remote end.
      90a6a9b6
  5. 18 Jul, 2012 1 commit
  6. 17 Jul, 2012 1 commit
  7. 14 Jul, 2012 3 commits
  8. 13 Jul, 2012 1 commit
  9. 12 Jul, 2012 4 commits
  10. 05 Jul, 2012 9 commits
  11. 03 Jul, 2012 3 commits
  12. 02 Jul, 2012 2 commits
    • Sriram Karra's avatar
      Use sane defaults for store and folder ids if they are null in config · 3ad3b9f3
      Sriram Karra authored
      This is the final step needed to support a 'sane' sync option
      with minimal configuration.
      
      Basically, if a user has just fetched ASynK, the most likely common case
      scenario will be to just sync his entire BBDB to the My Contacts folder
      in Google Contacts, or defaults contacts folder in Outlook to Google.
      With this commit that is possible.
      
      The way this is enabeld is any gc sync profile without a folder id is
      synhed to the My Contacts folder. If a store id is also missing a
      google contacts username is prompted for, and stored in the default storeid
      field. A similar "logical" thing is done with Outlook.
      3ad3b9f3
    • Sriram Karra's avatar