On Tue, 2004-10-05 at 10:32, Neil Conway wrote:
> I think the second hunk (arranging to read ~/.psqlrc before emitting the
> copyright message) is all that's necessary [...]
Patch applied.
-Neil
---(end of broadcast)---
TIP 5: Have you checked ou
On Mon, 2004-10-04 at 17:33, Sean Chittenden wrote:
> After seeing the "Welcome to psql 8.0.0beta3, the PostgreSQL
> interactive terminal." message, I finally got irritated enough at it to
> try and figure out how to silence it without using the -q option to
> psql(1).
I think the second hunk (
> There is no requirement that the program's output mention the
> license terms (perhaps you are thinking of the GPL?)
Yea,. I must have been... :)
... John
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http:/
John Hansen wrote:
Won't that violate the BSD licence?
No; if it did, psql's "-q" option would already violate the license. The
BSD license merely says:
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without a written
agreem
John Hansen wrote:
> Won't that violate the BSD licence?
The start-up message doesn't even contain any copyright information, so
no.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: the planner will ig
>
> After seeing the "Welcome to psql 8.0.0beta3, the PostgreSQL
> interactive terminal." message, I finally got irritated
> enough at it to try and figure out how to silence it without
> using the -q option to psql(1). The attached (trivial) patch
> fixes said problem so that one can add "\s
After seeing the "Welcome to psql 8.0.0beta3, the PostgreSQL
interactive terminal." message, I finally got irritated enough at it to
try and figure out how to silence it without using the -q option to
psql(1). The attached (trivial) patch fixes said problem so that one
can add "\set QUIET" to
