On Monday 26 February 2007 10:13, Bruce Momjian wrote:
> Warren Turkal wrote:
> > On Saturday 24 February 2007 16:47, Chad Wagner wrote:
> > > head pgsql/src/interfaces/perl5/Attic/test.pl.oldstyle,v
> > > head ? ?1.3;
> > > access;
> > > symbols
> > > ? ? ? ? Release-1-6-0:1.1.1.1
> > > ? ? ? ? creation:1.1.1.1
> > > ? ? ? ? creation:1.1.1; ? ?<<< What the heck happened here?
> > > locks; strict;
> > > comment @# @;
> >
> > Can a cvs maintainer please correct this file by adding a ";" after the
> > first "creation" line and removing the second "creation" line?
>
> Done. Any other problems?

This has not been fixed in the rsync repository. Here's one proof for one of 
the files.

[EMAIL 
PROTECTED]:~/projects/postgresql/pgsql-cvs/cvsroot/pgsql/src/interfaces/perl5/Attic$
 head -n 7 test.pl.newstyle,v
head    1.3;
access;
symbols
        Release-1-6-0:1.1.1.1
        creation:1.1.1.1
        creation:1.1.1;
locks; strict;
[EMAIL 
PROTECTED]:~/projects/postgresql/pgsql-cvs/cvsroot/pgsql/src/interfaces/perl5/Attic$

I have attached a patch for the files that needs to be applied within
the cvsroot/pgsql/src/interfaces/perl5/Attic directory in the
repository.

wt
-- 
Warren Turkal (w00t)
--- ApachePg.pl,v.old	2007-02-26 23:40:06.000000000 -0700
+++ ApachePg.pl,v	2007-02-26 23:41:16.000000000 -0700
@@ -2,8 +2,7 @@
 access;
 symbols
 	Release-1-6-0:1.1.1.1
-	creation:1.1.1.1
-	creation:1.1.1;
+	creation:1.1.1.1;
 locks; strict;
 comment	@# @;
 
--- test.pl.newstyle,v.old	2007-02-26 23:39:52.000000000 -0700
+++ test.pl.newstyle,v	2007-02-26 23:40:51.000000000 -0700
@@ -2,8 +2,7 @@
 access;
 symbols
 	Release-1-6-0:1.1.1.1
-	creation:1.1.1.1
-	creation:1.1.1;
+	creation:1.1.1.1;
 locks; strict;
 comment	@# @;
 
--- test.pl.oldstyle,v.old	2007-02-26 23:40:00.000000000 -0700
+++ test.pl.oldstyle,v	2007-02-26 23:41:07.000000000 -0700
@@ -2,8 +2,7 @@
 access;
 symbols
 	Release-1-6-0:1.1.1.1
-	creation:1.1.1.1
-	creation:1.1.1;
+	creation:1.1.1.1;
 locks; strict;
 comment	@# @;
 
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

Reply via email to