* Automatically filling in git send-email arguments based on an existing e-mail
@ 2013-10-02 8:25 Matthijs Kooijman
2013-10-02 10:19 ` John Keeping
0 siblings, 1 reply; 2+ messages in thread
From: Matthijs Kooijman @ 2013-10-02 8:25 UTC (permalink / raw)
To: git
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
Hi folks,
sometimes when I send a patch, I want to reply it to an existing e-mail,
using pretty much the same recipient list. Currently, I have to:
- copy-paste the message id for --in-reply-to header
- copy one address for --to
- copy the other addresses for the --cc's
Since I can't just chuck a list of addresses into --cc and I need to
quote every one because of the <> and spaces in there, this feels like
it's more tedious than needed.
It seems like there should be a weay to just copy paste the headers from
the original e-mail into the stdin of git send-email or a wrapper script
and let it sort things out from there.
Is there any interest in something like this? Does anyone else perhaps
already have such a script lying around?
(After writing this mail, I just noticed "[PATCH] git-send-email: two
new options: to-cover, cc-cover", which could help a bit to simplify
things, but not quite as far as I'm proposing here...)
Gr.
Matthijs
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Automatically filling in git send-email arguments based on an existing e-mail
2013-10-02 8:25 Automatically filling in git send-email arguments based on an existing e-mail Matthijs Kooijman
@ 2013-10-02 10:19 ` John Keeping
0 siblings, 0 replies; 2+ messages in thread
From: John Keeping @ 2013-10-02 10:19 UTC (permalink / raw)
To: Matthijs Kooijman, git
On Wed, Oct 02, 2013 at 10:25:25AM +0200, Matthijs Kooijman wrote:
> sometimes when I send a patch, I want to reply it to an existing e-mail,
> using pretty much the same recipient list. Currently, I have to:
>
> - copy-paste the message id for --in-reply-to header
> - copy one address for --to
> - copy the other addresses for the --cc's
>
> Since I can't just chuck a list of addresses into --cc and I need to
> quote every one because of the <> and spaces in there, this feels like
> it's more tedious than needed.
>
> It seems like there should be a weay to just copy paste the headers from
> the original e-mail into the stdin of git send-email or a wrapper script
> and let it sort things out from there.
>
>
> Is there any interest in something like this? Does anyone else perhaps
> already have such a script lying around?
I have been working on this for a while, but haven't yet got anything
into a suitable state for submission (and haven't made progress on it
for a while). My WIP is at:
https://github.com/johnkeeping/git/tree/format-patch-msgstore
The idea is to introduce a new helper protocol so that you can implement
various ways of finding a message given a message-id; I've implemented
one that finds the message from gmane.
What's there works in format-patch but not with send-email, which
implements message IDs itself rather than forwarding the arguments to
format-patch and I haven't had time to investigate changing send-email
to work with these patches.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-10-02 10:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-02 8:25 Automatically filling in git send-email arguments based on an existing e-mail Matthijs Kooijman
2013-10-02 10:19 ` John Keeping
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).