Re: Working with PostgreSQL source tree (was Re: Not ready for 8.3) - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Working with PostgreSQL source tree (was Re: Not ready for 8.3)
Date
Msg-id 2e78013d0705180424k7395a892sc4c66ae17235df26@mail.gmail.com
Whole thread Raw
In response to Re: Working with PostgreSQL source tree (was Re: Not ready for 8.3)  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers

On 5/18/07, Heikki Linnakangas <heikki@enterprisedb.com> 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
> diff between two versions as well.

Doesn't that confuse rsync?

I use cvsup. But thats not relevant here. Yes, cvsup would delete any
local tags/branches and sync the tree. But then I don't sync the tree very
often. And when I need to sync my work with CVS HEAD, I create
all the required diffs, sync the tree and reapply the patches (and commit
and tag) the tree again. Thats some work, but is I am OK with that
because as I said we don't need to sync with head that often.
 
Thanks

--
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Robert Mach
Date:
Subject: [GSOC] - I ntegrity check algorithm for data files
Next
From: Martijn van Oosterhout
Date:
Subject: Re: [GSOC] - I ntegrity check algorithm for data files