From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: pgsql-docs@postgresql.org
Subject: Re: outdated legal notice in SGML docs?
Date: Tue, 3 Jul 2012 12:02:11 -0400
Message-ID: <20120703160211.GE5578@momjian.us> (raw)
In-Reply-To: <1341089578.18033.7.camel@vanquo.pezone.net>
References: <4FB56426.7050409@kaltenbrunner.cc>
<1340140601.26286.28.camel@vanquo.pezone.net>
<20120629001405.GA19998@momjian.us>
<1341089578.18033.7.camel@vanquo.pezone.net>
On Sat, Jun 30, 2012 at 11:52:58PM +0300, Peter Eisentraut wrote:
> On tor, 2012-06-28 at 20:14 -0400, Bruce Momjian wrote:
> > On Wed, Jun 20, 2012 at 12:16:41AM +0300, Peter Eisentraut wrote:
> > > > This seems to be wrong in all branches and has the additional problem
> > > > that the Copyright year on the backbranches is always out-of-date - for
> > > > example:
> > > >
> > > > http://www.postgresql.org/docs/8.4/static/LEGALNOTICE.html
> > > >
> > > > will have 2009 for 8.4.11 which was released in 2012...
> > > >
> > > > any thoughts on what the correct way to fix this is?
> > >
> > > I've fixed this in all the active back branches. The copyright tool in
> > > src/tools/ does inform about doing these changes, but whoever does them
> > > has apparently not read that.
> >
> > I didn't think we wanted to update back branch copyright end dates
> > because that would effect thing like psql \copyright display, and the
> > risk didn't seem worth it.
> >
> > Do we want back-branches updated in the future?
>
> I think we should update at least COPYRIGHT and doc/src/sgml/legal.sgml,
> which are the most user-facing files. Updating all the source files is
> probably not necessary.
OK, I updated the copyright tool to mention this for back branches.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachments:copyright.diff (text/x-diff, 557B) downloaddiff --git a/src/tools/copyright.pl b/src/tools/copyright.plnew file mode 100755index d78a8d8..b8b8761
*** a/src/tools/copyright.pl
--- b/src/tools/copyright.pl
*************** sub wanted {
*** 51,55 ****
untie @lines;
}
! print "Manually update doc/src/sgml/legal.sgml and src/interfaces/libpq/libpq.rc.in too\n";
--- 51,56 ----
untie @lines;
}
! print "Manually update doc/src/sgml/legal.sgml and src/interfaces/libpq/libpq.rc.in too.\n";
! print "Also update ./COPYRIGHT and doc/src/sgml/legal.sgml in all back branches.\n";
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, peter_e@gmx.net, stefan@kaltenbrunner.cc
Subject: Re: outdated legal notice in SGML docs?
In-Reply-To: <20120703160211.GE5578@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox