Op 06-06-17 om 16:00 schreef Fungi4All:
From: wool...@eeg.ccf.org
On Mon, Jun 05, 2017 at 06:59:20PM -0400, Fungi4All wrote:
> ONLY MORONS USE RETURN WITHIN THE SAME PARAGRAPH EVER
> SINCE TYPEWRITERS RUN OUT OF INK AND DIED.
https://tools.ietf.org/html/rfc1855
In html there is for line bre
From: wool...@eeg.ccf.org
On Mon, Jun 05, 2017 at 06:59:20PM -0400, Fungi4All wrote:
> ONLY MORONS USE RETURN WITHIN THE SAME PARAGRAPH EVER
> SINCE TYPEWRITERS RUN OUT OF INK AND DIED.
https://tools.ietf.org/html/rfc1855
In html there is for line break and for paragraph. How long or short
sho
On Mon, Jun 05, 2017 at 01:19:40PM +0200, Siard wrote:
> I do not quite agree. Bottom posting and top posting are different
> styles of responding; choosing between them depends on your purpose.
Regardless of this, the messages from that funguy person are unreadable.
It looks like he's using Micro
On Mon, 5 Jun 2017 13:19:40 +0200
Siard wrote:
> Ric Moore:
> > Fungi4All:
> > > Sorry for the top-post but I think it is appropriate
> >
> > It is not ever appropriate, no matter what you think. Ric
>
> I do not quite agree. Bottom posting and top posting are different
> styles of respon
On Monday, June 05, 2017 07:19:40 AM Siard wrote:
> Ric Moore:
> > Fungi4All:
> > > Sorry for the top-post but I think it is appropriate
> >
> > It is not ever appropriate, no matter what you think. Ric
>
> I do not quite agree. Bottom posting and top posting are different
> styles of responding;
Ric Moore:
> Fungi4All:
> > Sorry for the top-post but I think it is appropriate
>
> It is not ever appropriate, no matter what you think. Ric
I do not quite agree. Bottom posting and top posting are different
styles of responding; choosing between them depends on your purpose.
Especially in a c
On Sat, Jun 03, 2017 at 07:27:06PM -0400, Ric Moore wrote:
On 06/02/2017 10:41 AM, Fungi4All wrote:
Sorry for the top-post but I think it is appropriate
It is not ever appropriate, no matter what you think. Ric
I disagree. I think that top-posting is MOST appropriate when forwarding
a messag
On Sunday 04 June 2017 00:27:06 Ric Moore wrote:
> On 06/02/2017 10:41 AM, Fungi4All wrote:
> > Sorry for the top-post but I think it is appropriate
>
> It is not ever appropriate, no matter what you think. Ric
+1
Lisi
On 06/02/2017 10:41 AM, Fungi4All wrote:
Sorry for the top-post but I think it is appropriate
It is not ever appropriate, no matter what you think. Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Onl
patched due to this security issue on jessie.
This is one package as an example.
Original Message
Subject: Re: Proper sources list from Jessie > Stretch
Local Time: June 1, 2017 2:28 PM
UTC Time: June 1, 2017 11:28 AM
From: d...@randomstring.org
To: Dejan Jocic
debian-u
On Thu, Jun 01, 2017 at 09:19:29AM +0200, Dejan Jocic wrote:
> On 01-06-17, Fjfj109 wrote:
> > Hi - wondering if with a standard sources list in Jessie (or any stable):
> It is usually enough to change it to stretch, if you follow it up with
> all those update and upgrade commands. And read releas
On 01-06-17, Fjfj109 wrote:
> Hi - wondering if with a standard sources list in Jessie (or any stable):
>
> deb
> http://deb.debian.org/debian
> jessie main
> deb-src
> http://deb.debian.org/debian
> jessie main
>
> deb
> http://deb.debian.org/debian
> jessie-updates main
> deb-src
> http://deb.d
Hi - wondering if with a standard sources list in Jessie (or any stable):
deb
http://deb.debian.org/debian
jessie main
deb-src
http://deb.debian.org/debian
jessie main
deb
http://deb.debian.org/debian
jessie-updates main
deb-src
http://deb.debian.org/debian
jessie-updates main
deb
http://securit
13 matches
Mail list logo
