Re: Working with PostgreSQL source tree (was Re: [HACKERS] Not ready for 8.3)

2007-05-18 Thread Pavan Deolasee
On 5/18/07, Heikki Linnakangas [EMAIL PROTECTED] wrote: When I start working on a subject, I make a new checkout from the local repository to a designated directory under pg_sandbox-directory. For example, when I started working on the mvcc-safe cluster patch: ~/pg_sandbox$ cvs -d

Working with PostgreSQL source tree (was Re: [HACKERS] Not ready for 8.3)

2007-05-18 Thread Heikki Linnakangas
Greg Smith wrote: On Thu, 17 May 2007, David Fetter wrote: Would you be interested in providing this meat? You're uniquely qualified because your shins still smart from all the things you barked them on :) Unfortunately I'm temporarily on the other side of this problem; all the time I have

Re: Working with PostgreSQL source tree (was Re: [HACKERS] Not ready for 8.3)

2007-05-18 Thread Heikki Linnakangas
Pavan Deolasee wrote: For primitive version control, I make a diff after any significant changes: ~/pg_sandbox/pgsql.cluster$ cvs diff -cN cluster-mvcc-1.patch I usually commit each version and tag the tree. That helps me to get diff between two versions as well. Doesn't that confuse

Re: Working with PostgreSQL source tree (was Re: [HACKERS] Not ready for 8.3)

2007-05-18 Thread Pavan Deolasee
On 5/18/07, Heikki Linnakangas [EMAIL PROTECTED] wrote: Pavan Deolasee wrote: For primitive version control, I make a diff after any significant changes: ~/pg_sandbox/pgsql.cluster$ cvs diff -cN cluster-mvcc-1.patch I usually commit each version and tag the tree. That helps me to get