| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 15:01:40 |
| Message-ID: | 20090603150140.GA7172@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas escribió:
> On Tue, Jun 2, 2009 at 7:54 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> > I think these are the two usable options. They will probably end up
>
> ...wait a minute. I just went and Googled this git-new-workdir thing
> and it looks like it's almost exactly what we need. According to the
> docs, it lets you share the same local repository between multiple
> working copies, so all the commits are shared but the index is
> separate for each working directory. Assuming it works, that sounds
> just about perfect for Tom's use case, since it would allow
> cherry-picking of commits without an intervening push/pull cycle. Did
> you have some reason for passing over that as one of the usable
> options?
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2009-06-03 15:07:14 | Re: PostgreSQL Developer meeting minutes up |
| Previous Message | Bruce Momjian | 2009-06-03 14:48:58 | Re: Warnings in compile |