Re: Updated handling of the git repositories

On 2010-08-29 at 19:12 +0200, Thorsten Behrens wrote:
> Jan Holesovsky wrote:
> > OK - now, after some fixes I am much more confident in this framework,
> > and ask everyone to configure with --with-git for the development.
> > 
> Hi all,
> 
> while playing with the new framework a bit more, I found it kinda
> inconvenient that the stuff below ooo-build/clone is always a
> stand-alone repo. Let me explain: I tend to have several checkouts
> of ooo-build on my disk, on the one hand because I play with cross-
> cutting feature work (that would require costly recompilation when
> reverted), and on the other because I frequently at least need the
> last-released version around.
> 
> So initially, I configured the new-style ooo-build via ...
> --with-git=/local/shared-sources/clone, i.e. cloning from local repo
> copies. That's a lot faster, but pulling/pushing ends up in the
> local repos, so that sucks, and especially for pulling, can be a
> pretty hard-to-diagnose error (wtf?! I've just pulled - why don't I
> see the changes just announced by Joe Hacker?!).
> 
> Enter stage git-new-workdir - that's a script from the git/contrib,
> that creates a new working directory plus index from a local repo,
> but shares all the rest - so pulls / pushes e.g. all go to the
> original remote repo.
> 
> Attached is a patch that unconditionally makes use of
> git-new-workdir - I did not push that yet, as I may be yet unaware
> of nasty side-effects when using git-new-workdir. Still, I consider
> that pretty darn useful.
> 
> What do you think?
> 
> -- Thorsten