public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: George Barrick <gbarrick@walsh.edu>
To: "'cygwin-xfree@cygwin.com'" <cygwin-xfree@cygwin.com>
Subject: Re: most recent xfig-3.2.5b-2 broken.
Date: Sat, 25 Feb 2012 20:22:00 -0000	[thread overview]
Message-ID: <4B30AD0BED19E842AAE88DC3973649314F600A1538@mail3.walsh.edu> (raw)

Subj: most recent xfig-3.2.5b-2 broken.

                     2012.02.25.20:19:51 UT

cygwin-x folks,

      I mis-typed at the end of my message.
I should say something like: "hope that
XFIG developers can reproduce and find the
problem".  

      I would not want to burden the xorg-guys
with trivial stuff like this.  I realize that
not many folks use clunky old things like xfig
anymore; but if it works, I keep it.  My letter
will perhaps only help other dinosaurs like me,
should they have this problem with xfig.

George              gbarrick_at_walsh_dot_edu



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


             reply	other threads:[~2012-02-25 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 20:22 George Barrick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-25 20:07 George Barrick
2012-02-26  0:40 ` marco atzeri
2012-02-27 12:47   ` George Barrick
2012-02-27 13:14     ` marco atzeri
2012-02-27 14:36       ` George Barrick
2012-02-27 14:47         ` marco atzeri
2012-02-27 15:01           ` George Barrick
2012-02-27 15:05             ` marco atzeri
2012-02-27 16:21               ` George Barrick
2012-02-27 16:37                 ` marco atzeri
2012-02-27 19:34                 ` Yaakov (Cygwin/X)

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=4B30AD0BED19E842AAE88DC3973649314F600A1538@mail3.walsh.edu \
    --to=gbarrick@walsh.edu \
    --cc=cygwin-xfree@cygwin.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).