From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: User format functions - text properies get lost (XEmacs)
Date: Tue, 15 Oct 2002 11:24:11 +0200 [thread overview]
Message-ID: <874rboukas.fsf@crybaby.cs.uni-dortmund.de> (raw)
In-Reply-To: <n2m-g.k7kkviqv.fsf@morpheus.demon.co.uk>
Paul Moore <gustav@morpheus.demon.co.uk> writes:
> What's the next step for me if I want to get this included in Gnus?
> I'm happy to work with someone developing the code, but if it's left
> to me, it won't happen.
Did you sign the copyright papers? (I can't look on fencepost to
check, so I might ask people many times :-/).
How about you mail me the patch again after the paper signing has
happened? Then I'll commit it.
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-10-15 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 15:39 Paul Moore
2002-10-14 12:01 ` Kai Großjohann
2002-10-14 21:00 ` Paul Moore
2002-10-15 9:24 ` Kai Großjohann [this message]
2002-10-16 20:18 ` Paul Moore
2002-10-17 13:03 ` Kai Großjohann
2002-10-17 19:34 ` Paul Moore
2002-10-17 13:00 ` Kai Großjohann
2002-10-17 19:48 ` Paul Moore
2002-10-18 14:34 ` Kai Großjohann
2002-10-18 18:15 ` Paul Moore
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=874rboukas.fsf@crybaby.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).