From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Assistance with patching instructions on Worg
Date: Fri, 31 Jan 2014 15:33:37 -0600 [thread overview]
Message-ID: <CA+M2ft8dGaGT-PpbL3nyb+4beAQtpxmtwvFK8PdzWF884p9-SA@mail.gmail.com> (raw)
Greetings,
I've only contributed to Worg, not the Org manual. I want to submit a
change to the documentation per an earlier discussion.[1] I'm
attempting to follow the Worg suggestion for submitting patches.[2]
Here was my process
cd ~/.elisp/org.git
git pull
make clean && make
git branch org-src-preserve-whitespace
git checkout org-src-preserve-whitespace
emacs doc/org.texi
[make changes to documentation]
git commit -m "Update documentation to org-src-preserve-indentation."
git format-patch master
But no files were generated... Am I doing something incorrectly?
Here's the current output of =git status=
On branch org-src-preserve-whitespace
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: doc/org.texi
no changes added to commit (use "git add" and/or "git commit -a")
UPDATE: just on a whim, I did `git commit -am "notes"` and now it
works. Since the file exists, why is -am necessary vs. just -m? Or
perhaps another question is why Worg suggests just -m. Should/would
this work under some circumstance?
I can update Worg with -am if this is the proper/necessary way.
Thanks,
John
[1] https://lists.gnu.org/archive/html/emacs-orgmode/2014-01/msg01505.html
[2] http://orgmode.org/worg/org-contribute.html#sec-4
next reply other threads:[~2014-01-31 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 21:33 John Hendy [this message]
2014-01-31 21:50 ` Assistance with patching instructions on Worg Thomas S. Dye
2014-01-31 21:58 ` John Hendy
2014-01-31 22:23 ` Josiah Schwab
2014-01-31 22:34 ` John Hendy
2014-01-31 22:51 ` Nick Dokos
2014-01-31 22:57 ` Josiah Schwab
2014-01-31 22:59 ` John Hendy
2014-02-02 15:27 ` John Hendy
2014-02-02 17:28 ` Bastien
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=CA+M2ft8dGaGT-PpbL3nyb+4beAQtpxmtwvFK8PdzWF884p9-SA@mail.gmail.com \
--to=jw.hendy@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.