From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Robins Tharakan" <tharakan(at)gmail(dot)com> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: How do you manage versions of your own code ? |
Date: | 2008-02-06 08:24:46 |
Message-ID: | 937d27e10802060024q7ba76a1esef89888e95d43dbd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Feb 6, 2008 3:34 AM, Robins Tharakan <tharakan(at)gmail(dot)com> wrote:
> Hi all,
>
> After going a bit of back and forth on different versions that I am working
> on I think I might as well ask how do you guys work on an open-source
> development project once you are disconnected ?
>
> I mean, if I do a svn co and start working, it wouldnt allow me to check in
> a version since its not a distributedVCS. If I use bzr-svn, it does
> checkout, but I still can't check in a half-way state since it tries to dump
> the patch to the online SVN too which of course fails.
>
> Apart from the current issue of me not having submit rights, how did you
> guys work on this when you don't have submit rights to a non-distributed VCS
> ?
> Did you just keep storing revision patches and patch / revert on the latest
> checked out revision as and when you needed to switch to an older version of
> your code ?
>
> (Btw, by version here I meant an older half-way-state of my own working
> code, not the PgAdmin version)
I just keep multiple copies of the tree around if I'm working on more
than one large project at a time, and take periodic diff's against SVN
if I think I need to. I've never really found the need for a
distributed scm with pgAdmin.
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2008-02-06 08:48:17 | Re: How do you manage versions of your own code ? |
Previous Message | Robins Tharakan | 2008-02-06 03:34:46 | How do you manage versions of your own code ? |