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

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: "Greg Smith" <gsmith(at)gregsmith(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Working with PostgreSQL source tree (was Re: Not ready for 8.3)
Date: 2007-05-18 11:24:48
Message-ID: 2e78013d0705180424k7395a892sc4c66ae17235df26@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/18/07, Heikki Linnakangas <heikki(at)enterprisedb(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-05-18 11:29:23 Re: [GSOC] - I ntegrity check algorithm for data files
Previous Message Robert Mach 2007-05-18 10:52:20 [GSOC] - I ntegrity check algorithm for data files