Am Dienstag, 12. April 2011, 16:23:34 schrieb J. Daniel Schmidt:
On Tuesday 12 April 2011 15:57:13 Adrian Schröter wrote:
* See git merge request (usually I don't in time due to lack of notifications * git checkout merg... * git pull merge... * git pull --rebase * git push * go to the web interface, search it and mark it as merged * tar the directory * osc commit
Looks highly un-efficient to me for all these small packages [...]
A slap in the faces of all maintainers of small packages. Thanks.
So lets rather make it easier to use instead of circumventing it.
Feel free to discuss that with git / gitorious authors.
Sorry, but this is is no way a git/gitorious specific problem.
YaST for example is still in SVN and we also have to do several steps until we can do an "osc commit".
Just one quick idea: We could create a OBS plugi n that automatically pushes the changes to the files of a package (not every package, only marked ones) into an auto-generated git repo $somewhere. Then you can continue working like before and the current code is in a git repo outside on a non-OBS server.
And how would that help on merge stuff back ? It would just overwrite stuff which comes via a different route ? Can you name a single advantage when using git for such a single file project ? -- 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