From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio bug
Date: Tue, 23 Mar 2004 19:30:07 +0000 [thread overview]
Message-ID: <541327ff4b03ef9cd164b6b1a7cef1ea@juice.thebigchoice.com> (raw)
I've often noticed border droppings and other bits of crud left behind
Like Andrey says - does it matter really?
I would say that it's not very professional, if you'd paid someone to write it for you, you'd send it back until it was fixed.
It certainly doesn't affect any ability to work, though now I have an annoying white square on my desktop I can't get rid of !
next reply other threads:[~2004-03-23 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 19:30 matt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 18:53 andrey mirtchovski
2004-03-23 19:04 ` Russ Cox
2004-03-23 19:15 ` rog
2004-03-23 19:19 ` andrey mirtchovski
2004-03-23 19:30 ` rog
2004-03-23 19:45 ` rob pike, esq.
2004-03-23 23:49 ` Geoff Collyer
2004-03-24 4:35 ` rob pike, esq.
2004-03-24 7:54 ` Fco.J.Ballesteros
2004-03-23 19:50 ` rog
2004-03-23 19:51 ` rob pike, esq.
2004-03-23 19:47 ` rob pike, esq.
2004-03-23 20:09 ` boyd, rounin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541327ff4b03ef9cd164b6b1a7cef1ea@juice.thebigchoice.com \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).