Re: (ASCEND) TR status

["Clifford Donley" <cdonley@southeast.net>]

I suppose another (reasonable) question is, how to you learn there is one?

Clearly, there are different classes of Ascend customers -- who have access
to different levels of information. For instance, I've received responses,
to the effect, hey dumb-dumb, don'cha know about this?? And of course I
don't, despite having read everything that ultimately ends-up in my inbox.

Cliff

----------
> From: David Lesher <wb8foz@nrk.com>
> To: Ascend Users List <ascend-users@bungi.com>
> Subject: (ASCEND) TR status
> Date: Saturday, June 07, 1997 3:28 PM
> 
> How does one check on the status of an open TR?
> 
> Do you just assume they are unresolved until you see then
> mentioned in a Release Note or......?
> 
> -- 
> A host is a host from coast to coast.................wb8foz@nrk.com
> & no one will talk to a host that's close........[v].(301) 56-LINUX
> Unless the host (that isn't close).........................pob 1433
> is busy, hung or dead....................................20915-1433
> ++ Ascend Users Mailing List ++
> To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
> or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>

---

• Prev by Date: (ASCEND) python 'aview' utility enhanced
• Next by Date: (ASCEND) TR status
• Prev by thread: (ASCEND) TR status
• Next by thread: (ASCEND) python 'aview' utility enhanced
• Index(es):
  • Main
  • Thread