On Tue, 02 Nov 2010 23:02:56 +0100, Gert Faller <gertfal...@aliceadsl.fr> wrote:
bin/g (and it is in the bin dir of your root checkout) basically iterates over all repositories in clone and performs an operation in each. So rather than updating each repo, you would do "bin/g pull" do update all repos. > 2) I've read that when updating 'clone', 'bin/g' must be run. > I don't find any 'g' in ./bin/. It really is there: http://cgit.freedesktop.org/libreoffice/build/tree/bin/g :) > 3) I don't know how to update easily the source in > 'build/libreoffice-3.2.99.2' Do build in the rawbuild/ directory as that operates directly on the git repositories. > 4) I edit code in 'clone/module' and 'git diff' from there but, for building, > I have to go to 'build/libreoffice-3.2.99.2/submodule' where I have done a > local > git, modify the patch (paths are too long in it eg : > a/module/submodule --> a/submodule), 'apply' it, 'build', 'apply -R', and > if > it's ok, get back to clone/module and undo my work (with the editor or with > 'apply -R') If you work in rawbuild and "make" from there, you can directly go into the directory, make changes, git add <files that you have changed>, git commit, and extract the patch with git format-patch HEAD^1. Hope that helps, I am sure there are even more efficient workflows. Sebastian
pgppWwCFhvgKi.pgp
Description: PGP signature
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice