From: Ivanov Dmitry <usr345@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re[2]: need detailed instructions for submitting the patch
Date: Tue, 10 Aug 2010 19:00:05 +0400 [thread overview]
Message-ID: <934840289.20100810190005@gmail.com> (raw)
In-Reply-To: <87y6cfb80y.fsf@gollum.intra.norang.ca>
Carsten, can you kindly add this to http://orgmode.org/worg/org-contribute.php#sec-3
"
To submit the patch follow the instructions:
This command will make a patch between the staging area
(in your computer), and the file you modified:
git diff -p org-whatever.el > org-whatever.el.diff
If you already committed your changes to your index (staging area),
then you should compare against a particular branch (in this example,
origin/master):
git diff -p origin/master org-whatever.el > org-whatever.el.diff
You email the output to the mailing list, adding [PATCH] to the
subject, and description of what you fixed or changed.
"
Should I add "> org-whatever.el.diff" to output the diff into a file, cause in Juans message it was missing?
It will be helpful to the new developers, I think.
next prev parent reply other threads:[~2010-08-10 15:00 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 ` Ivanov Dmitry [this message]
2010-08-10 15:30 ` Re[2]: " 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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=934840289.20100810190005@gmail.com \
--to=usr345@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.