From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Picons - still not quite right.
Date: Wed, 02 Jan 2002 14:35:19 -0500 [thread overview]
Message-ID: <2n1yh81r7s.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <microsoft-free.x4u1u4d6we.fsf@slackware.mynet.pc> (Steve Youngs's message of "Thu, 03 Jan 2002 03:01:05 +1000")
Steve Youngs <youngs@xemacs.org> writes:
[...]
> Fantastic! Thanks, ShengHuo. But I think something else has gone
> wrong now. I'm only seeing one of Didier's X-Faces. Both headers are
> there, but only one picture (the first one, his face, not the guitar
> one).
Fixed.
ShengHuo
next prev parent reply other threads:[~2002-01-02 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 11:34 Steve Youngs
2002-01-01 11:59 ` Lars Magne Ingebrigtsen
2002-01-01 12:35 ` Lars Magne Ingebrigtsen
2002-01-01 13:18 ` Steve Youngs
2002-01-01 13:38 ` Steve Youngs
2002-01-01 13:39 ` Lars Magne Ingebrigtsen
2002-01-01 14:07 ` Steve Youngs
2002-01-02 16:16 ` ShengHuo ZHU
2002-01-02 17:01 ` Steve Youngs
2002-01-02 19:35 ` ShengHuo ZHU [this message]
2002-01-02 20:55 ` Steve Youngs
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=2n1yh81r7s.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.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).