Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-24 Thread Magnus Hagander
> > That definitely looks weird to me. Unfortunatly, it's way > above me wrt > > CVS knowledge. I'm just going to have to live with it and > remember to > > delete that part from my diffs... > > The weird thing is that it's not happening for other people. > Have you tried blowing away the wh

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-22 Thread Tom Lane
"Magnus Hagander" <[EMAIL PROTECTED]> writes: > That definitely looks weird to me. Unfortunatly, it's way above me wrt > CVS knowledge. I'm just going to have to live with it and remember to > delete that part from my diffs... The weird thing is that it's not happening for other people. Have you

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-22 Thread Magnus Hagander
> > Strangely, if I try to do a "cvs add gram.c", it fails with cvs > add: > > `gram.c' added independently by second party I don't know what > this > > means. (Why "second party" and not "third party"?). Even if I > delete > > gram.c. Even if I remove it from .cvsignore. > > I think "cvs add"

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-20 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Strangely, if I try to do a "cvs add gram.c", it fails with > cvs add: `gram.c' added independently by second party > I don't know what this means. (Why "second party" and not "third > party"?). Even if I delete gram.c. Even if I remove it from > .cvs

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-20 Thread Alvaro Herrera
Magnus Hagander wrote: > > What does your CVS/Entries file look for that dir? > > It does contain both gram.c and gram.y. They look just the same (except > for version and date, of course). I don't know how it got there ;-) Is > it safe to just remove that? I don't know if it's safe, but my Entr

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-20 Thread Magnus Hagander
> > if I look into my cvs repository directory, it shows only > gram.y,v, > > with gram.c,v in Attic - which seems to make sense. Must be my > client > > that's gone crazy. In fact, mmy output ends up as: > > > > Index: src\backend\parser/gram.c > > > ===

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-19 Thread Alvaro Herrera
Magnus Hagander wrote: > if I look into my cvs repository directory, it shows only gram.y,v, with > gram.c,v in Attic - which seems to make sense. Must be my client that's > gone crazy. In fact, mmy output ends up as: > > Index: src\backend\parser/gram.c >

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-16 Thread Magnus Hagander
> > (I seem to have something funky in my cvs repo in general - doing a > > cvs diff gives me a *huge* diff for files like gram.c that > I thought > > weren't supposed to be in cvs at all. Any ideas on why that > would be? > > (I'm rsync:ing to a local repository and then running against that

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-16 Thread Tom Lane
"Magnus Hagander" <[EMAIL PROTECTED]> writes: > (I seem to have something funky in my cvs repo in general - doing a cvs > diff gives me a *huge* diff for files like gram.c that I thought weren't > supposed to be in cvs at all. Any ideas on why that would be? (I'm > rsync:ing to a local repository a

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-16 Thread Magnus Hagander
> > This patch adds a required include file to regress.c, > required to get > > at InvalidTransactionId. > > If that's needed, why isn't everybody else's build falling over too? Uh, because it's already included 4 lines up?! I must've been tired when I wrote that patch. Must've been something

Re: [HACKERS] [PATCHES] Include file in regress.c

2006-09-15 Thread Tom Lane
"Magnus Hagander" <[EMAIL PROTECTED]> writes: > This patch adds a required include file to regress.c, required to get at > InvalidTransactionId. If that's needed, why isn't everybody else's build falling over too? regards, tom lane ---(end of broad