From: Nico Schottelius <nicos-mutt@pcsystems.de>
To: James Simmons <jsimmons@transvirtual.com>
Cc: linuxconsole-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org, gpm@lists.linux.it,
salvador@inti.gov.ar
Subject: Re: [gpm]Reworking the selection API and moving it to userspace (gpm)?
Date: Sun, 17 Feb 2002 20:35:32 +0100 [thread overview]
Message-ID: <20020217193532.GB2208@schottelius.org> (raw)
In-Reply-To: <20020206203621.GB541@schottelius.org> <Pine.LNX.4.10.10202131018320.29350-100000@www.transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10202131018320.29350-100000@www.transvirtual.com>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
> > Possibly I have never heard about that and don't know anything particular about
> > it.
> > But in fact, improving something is generally good and if I have/get some
> > information about that, we could include it in gpm.
>
> It never really got out since I never got the chance to rework gpm.
You got it together with me.
> > Sounds good, so you're the person wrinting the patch for gpm ;)
>
> There are alos patches to get GPM working with the input api in CVS. I
> can post them.
Just send them.
--
Nico Schottelius
Please don't wonder, if you recieve answers to old mails from me.
I try to remove my huge backlog currently.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-17 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 20:24 Reworking the selection API and moving it to userspace (gpm)? Petr Baudis
2002-02-06 20:36 ` [gpm]Reworking " Nico Schottelius
2002-02-13 18:19 ` James Simmons
2002-02-17 19:35 ` Nico Schottelius [this message]
2002-02-13 18:14 ` Reworking " James Simmons
2002-02-17 19:20 ` [gpm]Re: " Nico Schottelius
-- strict thread matches above, loose matches on Subject: below --
2002-02-12 10:01 [gpm]Reworking " Alessandro Rubini
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=20020217193532.GB2208@schottelius.org \
--to=nicos-mutt@pcsystems.de \
--cc=gpm@lists.linux.it \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
--cc=salvador@inti.gov.ar \
/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