From: dsg@mitre.org (David S. Goldberg)
Subject: Another (minor) issue with the new forwarding
Date: 26 Feb 1999 16:31:27 -0500 [thread overview]
Message-ID: <m1bu2w8c0nk.fsf@blackbird.mitre.org> (raw)
I just forwarded a message with 0.79 and notice that my sig comes
after the inlined message. This caused some confusion on the part of
the recipient (a netscape user, if it matters) who thought that the
forwarded message was authored by me due to the sig placement and the
lack of delimiter at the end of the inlined message (it didn't help
that the forwarded message had no sig itself). I think in the old
case there was some variable that controlled whether the .sig would be
inserted before or after the forwarded message. Would it be possible
to bring that much back?
Thanks,
--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next reply other threads:[~1999-02-26 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-26 21:31 David S. Goldberg [this message]
1999-02-26 22:47 ` Lars Magne Ingebrigtsen
1999-03-01 16:29 ` David S. Goldberg
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=m1bu2w8c0nk.fsf@blackbird.mitre.org \
--to=dsg@mitre.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).