From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Script output in mail-source directory :prescript
Date: Sun, 30 Apr 2006 12:51:16 +0200 [thread overview]
Message-ID: <m3u08b1gm3.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87hd4gribv.fsf@frog.cs.hut.fi>
Timo Lilja <timo.lilja@hut.fi> writes:
> Nope, It didn't work for me but I modified it a bit and now it works:
Could you send me a diff against the current sources?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2006-04-30 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 21:20 Timo Lilja
2006-04-23 14:09 ` Lars Magne Ingebrigtsen
2006-04-26 5:56 ` Timo Lilja
2006-04-30 10:51 ` Lars Magne Ingebrigtsen [this message]
2006-05-13 17:04 ` Timo Lilja
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=m3u08b1gm3.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).