| From: | "Rod Taylor" <rbt(at)zort(dot)ca> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Dominic J(dot) Eidson" <sauron(at)the-infinite(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "John Gray" <jgray(at)azuli(dot)co(dot)uk>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Arch (was RE: Refactoring of command.c ) |
| Date: | 2002-02-28 13:56:36 |
| Message-ID: | 038a01c1c05f$bd5ded00$8001a8c0@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Imagine you want to develop a massive new feature for Postgres. You
just
> create a branch on your own machine, do all your changes, commits,
etc. and
> keep it current with the main branch. Then, you can merge it back
into the
> main tree... That way you can have a history of commits on your own
branch
> of the repo!
The same thing can be accomplished with CVS as well -- it's just not
as pretty. There is a reason that the FreeBSD group uses $FreeBSD$
and leaves $Id$ untouched.
Basically, check out of one, drop CVS directories, check into the
second, check out of the second, and when doing work with either
repository you specify which repo with the -D flag. Coupled with
the -j (merge) flag you can accomplish most tasks.
That said, if the work was thought through and beneficial you may be
able to obtain a branch in postgresql cvs to work with.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak | 2002-02-28 13:58:22 | Re: Oracle vs PostgreSQL in real life |
| Previous Message | Jean-Paul ARGUDO | 2002-02-28 13:39:47 | Re: Oracle vs PostgreSQL in real life |