Re: Serializable Isolation without blocking

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: nicolas(dot)barbier(at)gmail(dot)com, gsstark(at)mit(dot)edu, pgsql-hackers(at)postgresql(dot)org, laurenz(dot)albe(at)wien(dot)gv(dot)at
Subject: Re: Serializable Isolation without blocking
Date: 2010-01-06 21:33:51
Message-ID: 603c8f071001061333q247c20afyea355a4757d95e22@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 6, 2010 at 4:29 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
>> And use git so you can keep merging up to CVS HEAD easily.
>
> Regarding this, I was thinking that it would make sense to use a
> repository on git.postgresql.org to coordinate my work with any
> other people interested in the project.  I would clone from there
> for the repository on my own machine.  Does that make sense?  (I
> hope so, since I applied for a "serializable" repository there two
> or three days ago....)  I've read through some git tutorials, but
> there's a lot to digest and I'm not entirely sure this is a good way
> to proceed.

I think you should have users/kgrittner/postgres.git rather than
serializable.git. serializable sounds more like the branch name.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-01-06 21:35:12 Re: unresolved bugs
Previous Message Robert Haas 2010-01-06 21:30:53 Re: unresolved bugs