* Alvaro Herrera (alvhe...@commandprompt.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,
Tom Lane wrote:
Mark Mielke m...@mark.mielke.cc writes:
As a for example, you could have a local repo that you publish from.
Your work spaces could be from that local repo.
Yes, exactly. How do I do that? My complaint is that git fails to
provide a distinction between a repo and a
Tom Lane wrote:
I can't escape the feeling that we're missing something basic here.
It's allegedly one of git's great strengths that it allows you to easily
and quickly switch your attention among multiple development branches.
Well, so it does, if you haven't got any derived files to rebuild.
On Tue, Jun 2, 2009 at 9:46 PM, Mark Mielke m...@mark.mielke.cc wrote:
Tom Lane wrote:
I can't escape the feeling that we're missing something basic here.
It's allegedly one of git's great strengths that it allows you to easily
and quickly switch your attention among multiple development
On Tue, 2009-06-02 at 20:01 -0400, Tom Lane wrote:
Andres Freund and...@anarazel.de writes:
On 06/03/2009 01:39 AM, Tom Lane wrote:
But rebuilding the Linux kernel is hardly a zero-cost operation,
so how have Linus and co failed to notice this problem? There
must be some trick they're
101 - 105 of 105 matches
Mail list logo
