Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Subject: Soups again
Date: 16 Jun 1996 19:51:41 +0200	[thread overview]
Message-ID: <vafn323ab82.fsf@ls6.informatik.uni-dortmund.de> (raw)

Hi,

suppose I brew a soup and take it home with me.  There already is a
way to pack the replies to take them back to work.  WIBNI there was a
way to pack all `B m'ing I might have done, as well?

This way, I could brew a soup, take it home, look at the mails, decide
that one of my personal mails actually belongs to the foo project,
`B m' it to mail.projects.foo at home, then pack a reply packet, take
it back to work, and automagically, the mail would be `B m'ed to
mail.projects.foo at work, too.

Would that be possible?

Thanks in advance for any reply,
kai
-- 
Life is hard and then you die.


             reply	other threads:[~1996-06-16 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-16 17:51 Kai Grossjohann [this message]
1996-06-17  2:28 ` Lars Magne Ingebrigtsen

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=vafn323ab82.fsf@ls6.informatik.uni-dortmund.de \
    --to=grossjoh@charly.informatik.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).