From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Cc: Andrew Innes <andrewi@harlequin.co.uk>,
ntemacs-users@cs.washington.edu, ding@ifi.uio.no
Subject: Re: Gnus UU support
Date: 16 Jul 1996 20:49:03 +0200 [thread overview]
Message-ID: <w8su3v8dof4.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: Eric Swenson's message of (unknown date)
Eric Swenson <ejs@borland.com> writes:
> Thanks, Andrew for your explanation. It makes sense to me. Now, the
> more important question, should the Gnus sources (and indeed any Gnu
> Emacs sources) try to take this kind of stuff into account? Should I
> attempt to get the Gnus folks to incorporate my change into the Gnus
> sources?
Definitely. Mail me patches and I'll apply them.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
prev parent reply other threads:[~1996-07-16 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199607151248.NAA07124@propos.long.harlequin.co.uk>
1996-07-15 13:01 ` Eric Swenson
1996-07-16 12:16 ` Andrew Innes
1996-07-16 15:14 ` Steinar Bang
1996-07-16 13:58 ` Richard Pieri
1996-07-16 18:49 ` Lars Magne Ingebrigtsen [this message]
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=w8su3v8dof4.fsf@hler.ifi.uio.no \
--to=larsi@ifi.uio.no \
--cc=andrewi@harlequin.co.uk \
--cc=ding@ifi.uio.no \
--cc=ntemacs-users@cs.washington.edu \
/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).