config.xml conflicts with git config

[turicas]

I changed the remote origin of a repository by executing:

cd ~/Sparkleshare/some-repo
git remote rm origin
git remote add origin new-uri
git fetch --all

But Sparkleshare relies on ~/.config/sparkleshare/config.xml to syncronize the repository, which preserves the old origin. I think it's a bug - Sparkleshare should track any repository inside ~/Sparkleshare and use the git configuration of each repository to syncronize, instead of maintaining another meta-information (it could be a problem in future when not using Git, but if Sparkleshare will use its own configuration file, probably a good solution is to update this file with information returned by the Git repository).

[hbons]

SparkleShare can't keep track of any git repo. When you add a project a lot of custom configuration is added to make things run smoothly. The urls are stored in the config.xml as it's needed by the backend (mainly to be compatible with different types of backends). The fact that the url also exists in the repo itself is just the default behaviour of git-clone, it's not actually used.

[hbons]

Now that I think about it, it would be nice to only have to update the configuration in one place, so I'll let the repo config be updated by the config.xml on startup.