On Tuesday 12 April 2011 16:54:40 Adrian Schröter wrote:
Just one quick idea: [...]
And how would that help on merge stuff back ? It would just overwrite stuff which comes via a different route ?
Only if it is designed in a way that it overwrites stuff. Just like to put problems here to try to end the discussion or really interested and an answer? :) Here is one anyhow: Git has branches, so let this plugin push to a dedicated git branch eg. "OBS-controlled" and nobody will bother you when it overwrites stuff - its just a copy of what is in OBS.
Can you name a single advantage when using git for such a single file project ?
I didn't say you should use a git repo for a single file.
So here is the single advantage you asked for:
1. The code is not only in OBS but also at a second place out in the public.
This was Saschas only concern.
To solve it, just put the one file anywhere else in the public.
As the maintainance overhead seemed to be a problem I wanted to encourage to
find a different solution than just circumventing it.
Ciao,
Daniel
--
J. Daniel Schmidt