| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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-22 09:34:11 |
| Message-ID: | 1279791251.18768.2.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On ons, 2010-07-21 at 23:06 +0200, Dimitri Fontaine wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > 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.
>
> Ouch. Reading -hackers led me to thinking this had received a cleaning
> effort in the Makefiles, so that any generated file appears in the build
> directory. Sorry to learn that's not (yet?) the case.
It is, but not in the back branches.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-07-22 09:41:57 | Re: git config user.email |
| Previous Message | Peter Eisentraut | 2010-07-22 09:33:16 | Re: git config user.email |