public inbox for
 help / color / mirror / Atom feed
From: Christopher Faylor <>
Subject: Re: Cannot Execute urxvt after upgrade
Date: Sun, 22 Jul 2012 05:56:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, Jul 22, 2012 at 12:47:22AM -0500, Yaakov (Cygwin/X) wrote:
>On 2012-07-19 16:45, K Stahl wrote:
>> Just attempted to compile the latest (rxvt-unicode-9.15) and ran into
>> issues.  As I'm not completely versed in setting up the configuration
>> environment in Cygwin, I'm at a loss.  Seeing as there were numerous
>> packages that were updated as a result of the Perl version increment,
>> reverting to an older version is less than an ideal solution at this
>> point.
>> Could someone contact Yaakov and get his input on the situation?
>                         ^^^^^^
>Anyone else notice how I get blamed for everything around here? :-)

Yep.  I noticed.  That was an odd request for two reasons.  1) they
assumed that you have somethint to do with urxvt and 2) they thought
that you needed to be "contacted", presumably because you just aren't
active enough in the mailing list.

Or, maybe the mailing lists are just not reliable enough.  When are
you going to fix that anyway?


  reply	other threads:[~2012-07-22  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <BLU0-SMTP339E12561949F19FA8CC4A0CED90@phx.gbl>
     [not found]       ` <>
     [not found]         ` <BLU0-SMTP170955D78AEAA3C3B8B52C6CED90@phx.gbl>
     [not found]           ` <>
     [not found]             ` <>
2012-07-22  5:47               ` Yaakov (Cygwin/X)
2012-07-22  5:56                 ` Christopher Faylor [this message]
2012-07-22  6:03                   ` Christopher Faylor

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).