From: Francis Moreau <francis.moro@gmail.com>
To: Rupert Swarbrick <rswarbrick@gmail.com>
Cc: ding@gnus.org
Subject: Re: Sending patch with Gnus
Date: Fri, 17 Dec 2010 08:52:07 +0100 [thread overview]
Message-ID: <m2fwtwsuoo.fsf@gmail.com> (raw)
In-Reply-To: <ieecb6$daf$1@dough.gmane.org> (Rupert Swarbrick's message of "Fri, 17 Dec 2010 00:53:54 +0000")
Rupert Swarbrick <rswarbrick@gmail.com> writes:
> Francis Moreau <francis.moro@gmail.com> writes:
>>
>> BTW, if you needn't to modify the patches and only want to see them
>> before sending them then you can currently do this:
>
>>
>> M-! git format-patch --stdout HEAD~4 >/tmp/patch-set.mbox
>> C-x b *Group*
>> G f /tmp/patch-set.mbox
>>
>> This will create a nndoc group which contains all your patches as
>> articles.
>>
>> Then you can mark all of them and resend them with 'S D r'. But you
>> can't add Cc or Gcc header fields with this method.
>
> ... so I just tried this on another project's mailing list. Problem: the
> result isn't threaded.
Sure I didn't ask for to git.
>
> My 'ideal method' at the moment (inspired by the above) works something
> like this
>
[...]
>
> Notes:
>
> Sadly nndoc doesn't let us just edit the mbox inside gnus, although I
> suppose I'm not sure how that would work.
>
Again that's basically the whole point of the discussion.
>
> More sadly still (and possibly this is me being stupid?), if you
> realise something looks rubbish, the obvious approach of C-k killing
> the group, editing the mbox file and then doing G f again doesn't
> work, because Gnus cleverly caches the emails it seems (when I changed
> the number of emails I was getting the wrong ones!).
I don't think that's correct. If something need to be corrected, you
shouldn't modify the mbox file but instead fix your patchset inside your
repo and then regenerate the mbox file.
--
Francis
next prev parent reply other threads:[~2010-12-17 7:52 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 [this message]
2010-12-17 8:02 ` Rupert Swarbrick
2010-12-17 8:14 ` Francis Moreau
2010-12-17 16:30 ` Lars Magne Ingebrigtsen
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=m2fwtwsuoo.fsf@gmail.com \
--to=francis.moro@gmail.com \
--cc=ding@gnus.org \
--cc=rswarbrick@gmail.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).