From: Francis Moreau <francis.moro@gmail.com>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org, ding@gnus.org
Subject: Re: Sending patch with Gnus
Date: Wed, 15 Dec 2010 22:50:04 +0100 [thread overview]
Message-ID: <m2vd2uln8z.fsf@gmail.com> (raw)
In-Reply-To: <871v5i212s.fsf@tux.homenetwork> (Thierry Volpiatto's message of "Wed, 15 Dec 2010 22:11:39 +0100")
Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Francis Moreau <francis.moro@gmail.com> writes:
>>
>>> Since Gnus is using Git as SCM, I'm wondering if some of you have a
>>> magical function that can be used to send patch easily.
>>>
>>> For example, git-format-patch(1) generates a patch with all header
>>> fields set up such as "Subject, From..." and I'd like to create a new
>>> mail automatically from the generated patch using the header fields in
>>> the patch.
>>>
>>> Currently I'm starting a new mail and in the message body I'm inserting
>>> the output from git-format-patch(1) and then I do some clean up
>>> _manually_.
>>>
>>> Using git-send-email(1) with its ton of options is too complex for me
>>> when I need to send only 1 patch.
>>
>> This sounds like a good idea, but I think that it might belong more to
>> vc-mode than to Gnus, so I've Cc'd it to emacs-devel.
>>
>> Does the VC system have a general "make-an-email-from-this-patch"
>> mechanism?
> DVC have this.
> M-x dvc-export-via-mail
Well, I don't use VC (or DVC) mode because I just prefer using the SCM
directly since it allows to do much more things. And IIRC, VC mode do
some automatic things which can slow down a lot emacs when dealing with
large repos.
--
Francis
next prev parent reply other threads:[~2010-12-15 21:50 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 [this message]
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
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=m2vd2uln8z.fsf@gmail.com \
--to=francis.moro@gmail.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=thierry.volpiatto@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).