i am learning to use reply all, but having reply go to the list by default,
rather than the last person that replies might be useful as well.
On Thu, Jan 7, 2010 at 4:08 PM, Robert Haas wrote:
> On Thu, Jan 7, 2010 at 9:16 AM, Alvaro Herrera
> wrote:
> > Robert Haas escribió:
> >> On Wed, Jan 6
On Thu, Jan 7, 2010 at 9:16 AM, Alvaro Herrera
wrote:
> Robert Haas escribió:
>> On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis wrote:
>> > Can you please stop displaying the email addresses on bug reports? It's
>> > one
>> > thing to require an email address - it's another thing entirely to publ
Robert Haas escribió:
> On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis wrote:
> > Can you please stop displaying the email addresses on bug reports? It's one
> > thing to require an email address - it's another thing entirely to publish
> > it for spam address harvesting bots.
> >
> > This is an ex
On Wed, Jan 6, 2010 at 11:13 PM, Mike Landis wrote:
> Can you please stop displaying the email addresses on bug reports? It's one
> thing to require an email address - it's another thing entirely to publish
> it for spam address harvesting bots.
>
> This is an example page...
> http://archives.po
Mike Landis wrote:
Can you please stop displaying the email addresses on bug reports?
It's one thing to require an email address - it's another thing
entirely to publish it for spam address harvesting bots.
This is an example page...
http://archives.postgresql.org/pgsql-bugs/2009-12/msg00092.
Can you please stop displaying the email addresses on bug reports?
It's one thing to require an email address - it's another thing entirely
to publish it for spam address harvesting bots.
This is an example page...
http://archives.postgresql.org/pgsql-bugs/2009-12/msg00092.php
The e-mail addresses are listed on the URL in subject in the <...>
notation.
This makes the browser skip them as unknown tags and requires one to
look through the HTML source for addresses. How about < and > ?
Overall, the weblint's output for the page is:
index.php(2): illegal value
