Hi, i already asked that some days ago in the irc-channel where i've been asked to backport it to the mailing list :)
It would be really nice if you would use branches for each release you tag. That would ease upgrading the files on an productive system as you simply switch branches from e.g. [release-0.1] to [release-1.0]. I'd suggest reading [1] if some of you want to dig deeper into that (there are also bash-completion-scripts :)). Another thing would be to remove the config.php from VCS as there is an .gitignore-entry for it and only maintain the .example.php (this is really mixed up, IMO). Only using one root-.gitignore-file would add some clarity, too. Regards, Oluf [1]: <http://nvie.com/posts/a-successful-git-branching-model/> -- Bitte beachten Sie, dass dem Gesetz zur Vorratsdatenspeicherung zufolge jeder elektronische Kontakt mit mir sechs Monate lang gespeichert wird. Please note that according to the German law on data retention, information on every electronic information exchange with me is retained for a period of six months. _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
