Skip to content
Permalink
Browse files

Update mailinglist.html

the postgresql project is using @lists.postgresql.org now 
Also removed references to pg-foundry
should probably fix where commits go.
  • Loading branch information...
davecramer committed Sep 1, 2018
1 parent 1fff604 commit 556c93d35cc7f27abf2a98f087a85a76e7363c55
Showing with 2 additions and 11 deletions.
  1. +2 −11 docs/community/mailinglist.html
@@ -14,8 +14,7 @@ <h1>Mailing Lists</h1>
<div>
<ul>
<li><a href="#before">Before Mailing Anyone</a></li>
<li><a href="#general">General List - pgsql-jdbc@postgresql.org</a></li>
<li><a href="#commits">Commit Messages - jdbc-commits@pgfoundry.org</a></li>
<li><a href="#general">General List - pgsql-jdbc@lists.postgresql.org</a></li>
</ul>
</div>
</div>
@@ -69,16 +68,8 @@ <h2 class="underlined_10">General List - pgsql-jdbc@postgresql.org</h2>
<hr />

<a name="commits"></a>
<h2 class="underlined_10">Commit Messages - jdbc-commits@pgfoundry.org</h2>
<h2 class="underlined_10">Commit Messages</h2>
<div>
<p>
This mailing list is for people interested in carefully monitoring
the development process. The mailing list was active until the code
base was transferred to GitHub in late 2012. Every commit to this earlier
CVS repository sent out an email with the log message and links to diffs.
So the archive of this list, <a href="http://lists.pgfoundry.org/mailman/listinfo/jdbc-commits" target="_blank">pgfoundry site</a>,
holds the history of activity with the driver prior to 2013.
</p>
<p>
Currently activity on commits is best observed directly from the git
repository hosted with <a href="https://github.com/pgjdbc/pgjdbc" target="_blank">GitHub</a>.

0 comments on commit 556c93d

Please sign in to comment.
You can’t perform that action at this time.