Am Mittwoch, 2. Dezember 2009 00:52:25 schrieb Martin Mohring:
Hi,
Adrian, any Idea what we do with buildservice/dist? You are the co author of it...
I think we have two options: 1. move every file from dist into the propper api/dist, webui/dist, backend/dist .. 2. Or we make one git repository for the server part and move the dist there. #1 is maybe better for deploying servers out of git repos. #2 would be better to have everything together and to have one release tar ball. So far I personally feel that #2 is a better solution and even when we checkout everything on a server, we anyway can live via symlinks. Has anyone else an opinion about that ? bye adrian
Cheers, Martin
Stephan Kulow wrote:
Am Dienstag 01 Dezember 2009 schrieb Stephan Kulow:
Hi,
I started to group the SVN paths into GIT repositories. I'm not sure what branch we should keep and what history we can throw away (history as in outdated tags and long ago merged branches).
Please edit http://en.opensuse.org/User:Coolo:Gitmove - note that I can and I will rewrite history, just add a comment. E.g. if a software was imported with a typo and then moved I will rewrite this into a git that had the import right from the start. E.g. we should clean up
In case it's not clear: you're free to add repositories in grouping SVN paths. Basically all I need is a repository name and an idea what paths to have in there.
If you have only one toplevel directory (like build or osc), then the repository will be /buildservice/src/.../osc => / and if you have more than one toplevel directory, I will keep the toplevel directory so that .../src/backend will be /backend and .../src/sign will be /sign
Greetings, Stephan
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org