Gnus development mailing list
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
	 ding@gnus.org,  emacs-devel@gnu.org
Subject: Re: Sending patch with Gnus
Date: Wed, 15 Dec 2010 23:27:35 +0100	[thread overview]
Message-ID: <m2mxo6llig.fsf@gmail.com> (raw)
In-Reply-To: <87zks6zo58.fsf@member.fsf.org> (Tassilo Horn's message of "Wed, 15 Dec 2010 23:06:59 +0100")

Hello Tassilo,

Tassilo Horn <tassilo@member.fsf.org> writes:

> Francis Moreau <francis.moro@gmail.com> writes:
>
> Hi Francis,
>
>>> I do the same as Francis, e.g., insert and edit.  And at least with
>>> git, you should write your accompanying prose text below the
>>> signature.  That's a bit awkward, but it allows to pipe the complete
>>> email to "git am" (is it am?) without having to extract the patch
>>> manually first.
>>
>> I'm not sure to understand this.
>>
>> What do you mean by "accompanying prose text" ?
>
> The text in which you explain for what it's good for, where you ask the
> list to review it, in contrast to the 1-line summary git puts in the
> subject and the following full commit message, which starts the mail.

Ah I see, then I think you should place such text like this:


  [PATCH] A cool patch to speed up Gnus ;)
  
  A full commit message
  
  ---
  
  The text placed here is usually a message that is addressed to the list
  but won't be part of the commit.
  
   texi/ChangeLog |    4 ++++
   texi/gnus.texi |    2 +-
   2 files changed, 5 insertions(+), 1 deletions(-)
  
  diff --git a/texi/ChangeLog b/texi/ChangeLog
  index 8c0fec4..bf494ee 100644
  --- a/texi/ChangeLog
  +++ b/texi/ChangeLog

  [...]
  
  -- 
  1.7.3.2

-- 
Francis



      reply	other threads:[~2010-12-15 22:27 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
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 [this message]

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=m2mxo6llig.fsf@gmail.com \
    --to=francis.moro@gmail.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=tassilo@member.fsf.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).