From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: Andrew Lunn <andrew.lunn@ascom.ch>, ecos-maintainers@ecos.sourceware.org
Subject: Re: New Assignment: AFTEK
Date: Mon, 28 Jun 2004 10:49:00 -0000 [thread overview]
Message-ID: <40DFF7BA.8080902@ecoscentric.com> (raw)
In-Reply-To: <40DFF4EA.3040207@eCosCentric.com>
Jonathan Larmour wrote:
> Andrew Lunn wrote:
>
>> On Mon, Jun 28, 2004 at 09:10:27AM +0100, Alex Schuilenburg wrote:
>>
>>> Attached.
>>>
>>> And before anyone asks, this is all that was sent in two seperate 1
>>> page faxes. The fax was stored electronically so the address
>>> resolution is a result of the sender's fax scanner. No list of files
>>> was provided.
>>
>>
>>
>> Mostly useless...
>>
>> We need to track down what this is for. I've no idea. It does not fit
>> to any contribution i know of which is in the pipeline.
>
>
> Ah, no I know this one (and you can see - barely - my name at the top of
> the first page). It's this contrib:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000068
> which doesn't contain Aftek either.
>
>> Googling for "aftek infosys eCos" only produces two old hits. If you
>> can make out the senders FAX numbers could you send a FAX back asking
>> them to telephone/email you so we can get this straightened out.
>
>
> I'll follow up by e-mail directly.
Ack! I assume you are going to ask for a second fax with the contents.
For the doc to be legal, the address should be clearly visible, which
it is not in this case. For now though, a fax should do until we
receive the original via post when this is should not be an issue since
I assume it is legible there :-)
-- Alex
next prev parent reply other threads:[~2004-06-28 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 8:10 Alex Schuilenburg
2004-06-28 8:25 ` Andrew Lunn
2004-06-28 10:37 ` Jonathan Larmour
2004-06-28 10:49 ` Alex Schuilenburg [this message]
2004-09-07 9:02 Alex Schuilenburg
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=40DFF7BA.8080902@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=jifl@eCosCentric.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).