| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Adam Haberlach <adam(at)newsnipple(dot)com> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Quick questions regarding patches (and BeOS patch Q) |
| Date: | 2000-06-19 16:09:17 |
| Message-ID: | Pine.BSF.4.21.0006191308160.1098-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Mon, 19 Jun 2000, Adam Haberlach wrote:
> What is a good way to create patches? Can/should I use
> the `cvs diff` command? Should I have parallel orig/new source
> trees?
context diffs are a must, unified cause too many problems ... cvs diff -c
should do it ...
> In continuation of the BeOS thread, would anyone scream
> bloody murder if I created a smaller patch that just affected
> libpq, to at least get frontend support into the tree for the
> time being?
As long as nobody can see anything that it would break ... in general, its
much much easier to get a series of smaller patches in then one big one,
as its easier/faster for someone to go through and see any problems it
might cause ...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-06-19 16:17:14 | RE: Big 7.1 open items |
| Previous Message | Bruce Momjian | 2000-06-19 13:39:09 | Re: odbc patches |