Re: managing git disk space usage

Aidan Van Dyk <aidan(at)highrise(dot)ca> writes:
> * Robert Haas <robertmhaas(at)gmail(dot)com> [100720 13:04]:
>
>> 3. Clone the origin once. Apply patches to multiple branches by
>> switching branches. Playing around with it, this is probably a
>> tolerable way to work when you're only going back one or two branches
>> but it's certainly a big nuisance when you're going back 5-7 branches.
>
> This is what I do when I'm working on a project that has completely
> proper dependancies, and you don't need to always re-run configure
> between different branches. I use ccache heavily, so configure takes
> longer than a complete build with a couple-dozen
> actually-not-previously-seen changes...
>
> But *all* dependancies need to be proper in the build system, or you end
> up needing a git-clean-type-cleanup between branch switches, forcing a
> new configure run too, which takes too much time...
>
> Maybe this will cause make dependancies to be refined in PG ;-)

Well, there's also the VPATH possibility, where all your build objects
are stored out of the way of the repo. So you could checkout the branch
you're interrested in, change to the associated build directory and
build there. And automate that of course.

Regards,
--
dim