Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: saving copies of the messages sent in Gnus
Date: Tue, 03 Jan 2012 22:37:16 +0100	[thread overview]
Message-ID: <m362gsfoxf.fsf@stories.gnus.org> (raw)
In-Reply-To: <b4m4nxsx1x6.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 25 Nov 2011 13:26:44 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Gcc to a `sent' group might be useful, I thought afterward.  So,
> I tried making `gnus-summary-resend-message' do Gcc.  The new
> user option `gnus-gcc-inhibit-gcc-self-when-resending' controls
> whether to archive resent articles in the identical group or not.
> The default value is t, i.e. inhibit.  A patch is below.

It's a good idea.

Should we open an "mgnus" branch so that we don't lose patches like
this, perhaps?  Or perhaps it would make more sense to open an "ngnus"
branch for bug-fixes only, and continue with development on the
trunk...  I don't know...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2012-01-03 21:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87sjlw9c9d.fsf@violet.siamics.net>
     [not found] ` <87r51fvytj.fsf@marauder.physik.uni-ulm.de>
     [not found]   ` <b4m7h36lx6n.fsf@jpl.org>
     [not found]     ` <86aa82vwg4.fsf@gray.siamics.net>
2011-11-25  4:26       ` Katsumi Yamaoka
2012-01-03 21:37         ` Lars Magne Ingebrigtsen [this message]
2012-01-05  7:28           ` Katsumi Yamaoka
2012-01-05 10:43             ` Steinar Bang
2012-01-09 19:40               ` Steinar Bang
2012-02-02  1:27             ` Katsumi Yamaoka
2012-01-07  2:04           ` Ted Zlatanov
2012-01-07  6:21             ` Lars Magne Ingebrigtsen
2012-01-07 13:03               ` Ted Zlatanov

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=m362gsfoxf.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.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).