From: Dan Davison <davison@stats.ox.ac.uk>
To: nicholas.dokos@hp.com
Cc: Ivanov Dmitry <usr345@gmail.com>,
emacs-orgmode@gnu.org, Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: need detailed instructions for submitting the patch
Date: Tue, 10 Aug 2010 14:11:18 -0400 [thread overview]
Message-ID: <87sk2mwd6h.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <19674.1281463074@gamaville.dokosmarshall.org> (Nick Dokos's message of "Tue, 10 Aug 2010 13:57:54 -0400")
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?
+ attachment type text/x-diff?
+ attach using C-c C-a in gnus but choose "inline" rather than as
"attachment"?
+ paste inline?
+ paste inline with special gnus separators --8<-- ?
does it matter how the patch file is named?
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?
Dan
>
> Then when the patch hits mainline (or it is irrevocably rejected), get
> rid of the branch:
>
> git branch -D topic-branch
>
> Nick
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2010-08-10 18:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 21:59 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 [this message]
2010-08-10 20:39 ` David Maus
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=87sk2mwd6h.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--cc=usr345@gmail.com \
--subject='Re: need detailed instructions for submitting the patch' \
/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
Code repositories for project(s) associated with this 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).