Selon Sebastian Spaeth :
>
> If you work in rawbuild and "make" from there, you can directly go into
> the directory, make changes, git add , 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
>
Hi
On Tue, 02 Nov 2010 23:02:56 +0100, Gert Faller 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
> I'am very new to git (only have used sometimes 'git clone' before) , and I
don't get it very well...
I am brand new to git and I felt confused alot until I found this --
http://wiki.documentfoundation.org/Development#Using_Git_for_LibreOffice_development
-- this ref explains many things
On Tue, Nov 02, 2010 at 11:02:56PM +0100, Gert Faller
wrote:
> 1) I update the 'clone' directory often. No problem with that.
> 2) I've read that when updating 'clone', 'bin/g' must be run.
>I don't find any 'g' in ./bin/.
> 3) I don't know how to update easily the source in
> 'build/libreof
