Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: drafts/queue and edited messages.
Date: 09 Mar 2001 15:08:00 -0800	[thread overview]
Message-ID: <m3d7bq8rt6.fsf@gnus.cvs.983032537> (raw)


This has come up a few times but I've lost track of any resolution to
it.

Using a semi-stock outgoing message archive and then several
particular groups where I've set gcc in the group params.

If I happen to edit a message that has collected in
~/News/drafts/queue

The archived or gcc'ed copy is no longer a faithful copy.

Is this just unavoidable or can we have code that governs drafts/queue
and knows where the message came from, its file number and whether
it is gcc'ed?  If so write them back to the sending group overwriting
the original.  Maybe the same with the global archive, if the message
is not gcc'ed.

Maybe make it a requirement for this code that all groups involved be
under that same backend.  Avoiding that major problem.


             reply	other threads:[~2001-03-09 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 23:08 Harry Putnam [this message]
2001-03-09 23:17 ` ShengHuo ZHU
2001-03-10  0:06   ` Harry Putnam

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=m3d7bq8rt6.fsf@gnus.cvs.983032537 \
    --to=reader@newsguy.com \
    /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).