| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Managing multiple branches in git |
| Date: | 2009-06-03 00:33:20 |
| Message-ID: | 20090603003320.GB8123@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Alvaro Herrera (alvherre(at)commandprompt(dot)com) wrote:
> This doesn't fully work because some files are created in the source
> directory even when building outside (e.g. src/backend/parser/scan.c)
Sure, there's a couple files here and there, but those could probably be
handled through gitignore, similar to our .cvsignore files..? I dunno,
was just a thought towards this specific item Tom that was talking about
(build-generated files in the source tree).
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-06-03 00:54:01 | Re: It's June 1; do you know where your release is? |
| Previous Message | Robert Haas | 2009-06-03 00:31:49 | Re: Managing multiple branches in git |