Thread: pgsql/src/interfaces/ecpg/preproc keywords.c p ...
pgsql/src/interfaces/ecpg/preproc keywords.c p ...
From
meskes@postgresql.org (Michael Meskes)
Date:
CVSROOT: /cvsroot Module name: pgsql Changes by: meskes@postgresql.org 02/06/30 05:34:14 Modified files: src/interfaces/ecpg/preproc: keywords.c pgc.l preproc.y Log message: Committing parser changes. Note, however, that the development bison seems ot have a problem on my home machine. So thesego in untested for the time being. But at least I have them in the archive. Michael
meskes@postgresql.org (Michael Meskes) writes: > Committing parser changes. Note, however, that the development bison seems ot have a problem on my home machine. Sothese go in untested for the time being. But at least I have them in the archive. Weren't these changes supposed to go on a branch, until a working bison release is available? It sure looks from here like you committed them on HEAD. regards, tom lane
On Sun, Jun 30, 2002 at 12:06:21PM -0400, Tom Lane wrote: > Weren't these changes supposed to go on a branch, until a working bison > release is available? Sure they were. > It sure looks from here like you committed them on HEAD. ARGH! Not sure what happened. I thought I had set it up correctly. No idea what went wrong as I tried to set it up as Thomas said. Again I'm not really knowledgeable in using cvs, so I guess I made a stupid mistake. But I hope the files are restorable, aren't they? Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Michael Meskes <meskes@postgresql.org> writes: > Again I'm not really knowledgeable in using cvs, so I guess I made a > stupid mistake. But I hope the files are restorable, aren't they? Just re-commit the prior version. regards, tom lane
Tom Lane wrote: > Michael Meskes <meskes@postgresql.org> writes: > > Again I'm not really knowledgeable in using cvs, so I guess I made a > > stupid mistake. But I hope the files are restorable, aren't they? > > Just re-commit the prior version. Another options is to do a 'cvs diff -c -rX -rY where X and Y are the two most recent versions. That will generate a patch, and you can 'patch -R' to apply the reversed patch and commit that new version. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
> > It sure looks from here like you committed them on HEAD. > ARGH! Not sure what happened. I thought I had set it up correctly. No > idea what went wrong as I tried to set it up as Thomas said. Michael, do you want some assistance getting started on the branch? I'm pretty sure that my instructions were accurate, but I can do a sample update on, say, the Makefile and send you a transcript... - Thomas
On Sun, Jun 30, 2002 at 01:58:49PM -0400, Tom Lane wrote: > Michael Meskes <meskes@postgresql.org> writes: > > Again I'm not really knowledgeable in using cvs, so I guess I made a > > stupid mistake. But I hope the files are restorable, aren't they? > > Just re-commit the prior version. Done. It shoudl be okay again now. Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
On Sun, Jun 30, 2002 at 09:15:19PM -0700, Thomas Lockhart wrote: > Michael, do you want some assistance getting started on the branch? I'm > pretty sure that my instructions were accurate, but I can do a sample I'm sure your instructions were accurate too. Somehow I managed to make a mistake. I tried again a few minutes ago and it seems to have worked now. Thanks a lot. Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!