From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Externally feeding the drafts folder -- git format-patch integration
Date: Thu, 27 Feb 2014 09:32:28 -0500 [thread overview]
Message-ID: <87a9dceidf.fsf@lifelogs.com> (raw)
In-Reply-To: <87eh2v5wr9.fsf@denkblock.local>
On Sat, 22 Feb 2014 10:20:42 +0100 Elias Oltmanns <eo@nebensachen.de> wrote:
...
EO> 2. Generate a patch series from the local commits with a command like
EO> $ git format-patch --thread --cover-letter --to developer@example.org \
EO> --cc devel@list.example.org --stdout > ~/Mail/git.spool
EO> 3. Fire up gnus and have the patch series stored in ~/Mail/git.spool
EO> magically appear in the drafts group so I can edit the cover letter
EO> and possibly annotate some of the other messages too before sending
EO> the off.
I don't know that piece, sorry. But it can probably be automated with
some effort. I know the drafts group is special. "Lars" special.
You could maybe start an gnus-slave session with a new buffer in
message-mode, insert the message, and save it as a draft?
EO> 4. Replies to those e-mails should go to the corresponding devel folder
EO> by means of gnus-registry-split-fancy-with-parent.
That's pretty easy. You can force-feed the gnus-registry data about a
specific message ID. So if you can get the message's message ID, no
worries. And if you go through the gnus-slave session or something
similarly "Gnus-ish" the gnus-registry should notice anyhow.
Ted
next prev parent reply other threads:[~2014-02-27 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 9:20 Elias Oltmanns
2014-02-27 14:32 ` Ted Zlatanov [this message]
2014-03-04 10:40 ` lee
2014-03-04 16:25 ` Elias Oltmanns
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=87a9dceidf.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).