From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(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 16:13:41 |
Message-ID: | 4A26A135.4050404@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Page wrote:
> On Wed, Jun 3, 2009 at 4:01 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
>
>
>> Well, it sounds about perfect for my use case too (which is
>> approximately the same as Tom's), but the description makes it sound
>> unsupported. It doesn't work on Windows which doesn't bother me
>> personally but may be a showstopper more generally.
>>
>
> It's not a showstopper for me. Can't speak for Magnus, Andrew or
> anyone else working on Windows though. I imagine those two are the
> most likely to have issues if they're back-patching - and that should
> just be a matter of disk space.
>
>
Yeah, AFAIK Magnus doesn't commit direct from Windows, and neither do I,
and this should not be a showstopper for anyone who isn't a committer.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-06-03 16:14:40 | Re: Managing multiple branches in git |
Previous Message | Joshua D. Drake | 2009-06-03 16:09:53 | Re: Managing multiple branches in git |