From: skip.tavakkolian@gmail.com (Skip Tavakkolian)
Subject: [9fans] drawterm bug
Date: Tue, 22 Mar 2011 10:59:05 -0700 [thread overview]
Message-ID: <AANLkTiniohdpyYoaDRTMhifPTO+gAqzuq9FjtA5WZBt2@mail.gmail.com> (raw)
In-Reply-To: <2fb1ffc42e33bf0578de68d82f5863bc@ladd.quanstro.net>
i feel your pain. i went through the process for a patch queue to support ARM.
FYI, when i mentioned this to Russ, he said I could email him the
patch. I think if it's small enough it's probably the best way.
On Tue, Mar 22, 2011 at 10:40 AM, erik quanstrom <quanstro at quanstro.net> wrote:
> that was an ordeal. ?here's the patch queue
>
> https://bitbucket.org/quanstro/drawterm-fixes/changesets
>
> - erik
>
>
next prev parent reply other threads:[~2011-03-22 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 15:36 erik quanstrom
2011-03-22 14:40 ` erik quanstrom
2011-03-22 17:40 ` erik quanstrom
2011-03-22 17:59 ` Skip Tavakkolian [this message]
2011-03-22 18:57 ` erik quanstrom
2011-03-22 17:45 ` Jeff Sickel
2011-03-22 17:51 ` erik quanstrom
2011-03-22 18:02 ` Jeff Sickel
2011-03-25 19:48 ` Ethan Grammatikidis
2011-03-25 20:09 ` dexen deVries
2011-03-25 21:00 ` Jeff Sickel
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=AANLkTiniohdpyYoaDRTMhifPTO+gAqzuq9FjtA5WZBt2@mail.gmail.com \
--to=skip.tavakkolian@gmail.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 NNTP newsgroup(s).