| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: managing git disk space usage |
| Date: | 2010-07-21 19:29:04 |
| Message-ID: | 1279740453-sup-1810@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Dimitri Fontaine's message of mié jul 21 15:00:48 -0400 2010:
> 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.
This does not work as cleanly as you suppose, because some "build
objects" are stored in the source tree. configure being one of them.
So if you switch branches, configure is rerun even in a VPATH build,
which is undesirable.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-07-21 19:31:11 | Re: documentation for committing with git |
| Previous Message | Robert Haas | 2010-07-21 19:26:47 | Re: documentation for committing with git |