emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Maus <dmaus@ictsoc.de>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: Bastien <bastien.guerry@wikimedia.fr>,
	nicholas.dokos@hp.com, emacs-orgmode@gnu.org,
	Ivanov Dmitry <usr345@gmail.com>
Subject: Re: Re: need detailed instructions for submitting the patch
Date: Tue, 10 Aug 2010 22:39:37 +0200	[thread overview]
Message-ID: <87d3tqw6ba.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <87sk2mwd6h.fsf@stats.ox.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 2003 bytes --]

Dan Davison wrote:
>Nick Dokos <nicholas.dokos@hp.com> writes:

>> Bastien <bastien.guerry@wikimedia.fr> wrote:
>>
>>
>>> > For example, I have a modified file org-whatever.el. What commands
>>> > must I run?
>>>
>>> Please follow the instructions on Worg and let us know what is not
>>> crystal-clear -- that will help improve the doc if necessary.
>>>
>>
>> I think Dmitry is asking for the git commands and I'm not sure those
>> are described anywhere on Worg.
>>
>> Something like this perhaps:
>>
>>          # create a topic branch to deal with a specific topic: use
>>          # a descriptive name!
>>          git checkout -b topic-branch-foo master
>>          <make changes specific to topic>
>>          git commit -a
>>          git format-patch
>>          <send out patch in email to appropriate mailing list>

>One point I'm not yet clear on:

>For the patchwork system, what methods of inclusion of patch in email
>are acceptable?

>+ attachment type text/plain?
Works.

>+ attachment type text/x-diff?
Works.

>+ attach using C-c C-a in gnus but choose "inline" rather than as
>  "attachment"?

"inline" or "attachment" is irrelevant: It is just a hint to a
displaying MUA how to visualize an attachment (Cf. RFC2183: The
Content-Disposition Header Field).

>+ paste inline?
Should work.

>+ paste inline with special gnus separators --8<-- ?
Dunno.

>does it matter how the patch file is named?
AFAIK it doesn't.

>Also, what requirements are there on how to *reply* so that your message
>gets lumped by patchwork into the same patch item, rather than creating
>a new item? Can the subject line be modified?

AFAIK the subject line doesn't matter because what identifies a
message (for patchtracker and in general) is the message-id header
field.  So it should be a proper reply to the message: Using the
message-id header field in the in-reply-to and references header
field.

Best,
  -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-08-10 20:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 21:59 need detailed instructions for submitting the patch Ivanov Dmitry
2010-08-09 23:36 ` Juan
2010-08-10  0:55   ` Bernt Hansen
2010-08-10 15:00     ` Re[2]: " Ivanov Dmitry
2010-08-10 15:30       ` Bastien
2010-08-10 17:33         ` Re[2]: " Ivanov Dmitry
2010-08-10 17:47           ` Bastien
2010-08-10 17:57             ` Nick Dokos
2010-08-10 18:11               ` Dan Davison
2010-08-10 20:39                 ` David Maus [this message]
2010-08-10 18:14               ` Re[2]: Re[2]: " Ivanov Dmitry
2010-08-10 18:29                 ` Nick Dokos
2010-08-10 18:29                 ` Thomas S. Dye
2010-08-11  5:09                   ` ReRe[2]: " Noorul Islam K M
2010-08-11 22:16                 ` Re[2]: " Bastien
2010-08-11 23:00               ` Bastien
2010-08-10 15:34       ` Eric Schulte

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d3tqw6ba.wl%dmaus@ictsoc.de \
    --to=dmaus@ictsoc.de \
    --cc=bastien.guerry@wikimedia.fr \
    --cc=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=usr345@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).