Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Sending patch with Gnus
Date: Fri, 17 Dec 2010 17:30:07 +0100	[thread overview]
Message-ID: <m3oc8ke50w.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ieecb6$daf$1@dough.gmane.org>

Rupert Swarbrick <rswarbrick@gmail.com> writes:

> (3) Now open up the mbox file in emacs and edit the first email so it
>     has a nice covering letter explaining why you're spamming the
>     mailing list.
>
> (4) Now do 'G f tmp.mbox' from the *Group* buffer. If everything looks
>     hunky-dory (and threaded!), do the 'S D r' thang.

Oh, OK, now I think I understand what all y'all are saying.  So you have
a mbox file (possibly created by git) containing many messages.  You
want to look at all the messages, and possibly edit them, and then send
off all the messages separately?

That sounds quite useful, yes.  But couldn't this be implemented as an
ephemeral nnfolder group?  That would allow you to edit any or all of
the articles (for instance, you'd want a command to add a References
header to all messages following the "cover letter", and you may want to
fiddle around with the patch series itself (perhaps `B DEL' one patch in
the series).

And then you'd just need a command to send all the messages in the
summary buffer, and you'd be done.  :-)

So this wouldn't really be a gnus-dired thing, but basically just a
summary minor mode with additional commands for editing/mangling the
nnfolder. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  parent reply	other threads:[~2010-12-17 16:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 16:05 Francis Moreau
2010-12-15 19:21 ` Lars Magne Ingebrigtsen
2010-12-15 21:11   ` Thierry Volpiatto
2010-12-15 21:50     ` Francis Moreau
2010-12-15 21:54       ` Lars Magne Ingebrigtsen
2010-12-15 22:13         ` Francis Moreau
2010-12-16  6:09     ` Leo
2010-12-16 10:01       ` Francis Moreau
2010-12-16 13:07         ` Leo
2010-12-16 13:12           ` Leo
2010-12-16 20:20           ` Francis Moreau
2010-12-17  0:53         ` Rupert Swarbrick
2010-12-17  1:03           ` "Purging" nndoc group, was: " Rupert Swarbrick
2010-12-17  7:52           ` Francis Moreau
2010-12-17  8:02             ` Rupert Swarbrick
2010-12-17  8:14               ` Francis Moreau
2010-12-17 16:30           ` Lars Magne Ingebrigtsen [this message]
2010-12-17 19:54             ` Francis Moreau
2010-12-17 19:57               ` Lars Magne Ingebrigtsen
2010-12-17 20:04                 ` Francis Moreau
2010-12-17 20:14                   ` Štěpán Němec
2010-12-16 15:53       ` Lars Magne Ingebrigtsen
2010-12-16 17:16         ` Leo
2010-12-16 17:19           ` Lars Magne Ingebrigtsen
2010-12-17  6:29             ` Štěpán Němec
2010-12-17  7:33               ` Francis Moreau
2010-12-18 20:34               ` Reiner Steib
2010-12-19  6:50                 ` Štěpán Němec
2010-12-17 10:01             ` Leo
2010-12-15 21:27   ` Tassilo Horn
2010-12-15 21:41     ` Francis Moreau
2010-12-15 22:06       ` Tassilo Horn
2010-12-15 22:27         ` Francis Moreau

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=m3oc8ke50w.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@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).