From: John Hendy <jw.hendy@gmail.com>
To: Josiah Schwab <jschwab@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Assistance with patching instructions on Worg
Date: Sun, 2 Feb 2014 09:27:49 -0600 [thread overview]
Message-ID: <CA+M2ft86X_4t6eEX-W59fXT9H-5hEfm6+Z-VyGaQMLjBmW2bAQ@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft9e+s57FcaxrPh-pZ++sqYGvvD0dsSU-CqH=7tj4E6gVA@mail.gmail.com>
Just confirming the change of Worg. I used the same format specified
in the Worg git page:
- Changed page: http://orgmode.org/worg/org-contribute.html#sec-4-2
- Worg git referred to: http://orgmode.org/worg/worg-git.html
Having seen that page, I wondered if it should instructions to use
`git add file.ext` if files are created? I left that alone for now,
figuring that I'm at a lower-than-most level of git intelligence :)
By the way, I love that Worg updates immediately now!
John
On Fri, Jan 31, 2014 at 4:59 PM, John Hendy <jw.hendy@gmail.com> wrote:
> On Fri, Jan 31, 2014 at 4:57 PM, Josiah Schwab <jschwab@gmail.com> wrote:
>>
>> jw.hendy@gmail.com writes:
>>
>>> I was just following along with Worg, which doesn't mention doing
>>> that. I'm now thinking that `git add` must be implied in the line
>>> =make some changes (1)=?
>>
>> Yes, I agree; as written, there is an implicit `git add`. I think it
>> would be reasonable to make that explicit.
>
> Will do, and thanks for the quick assistance all!
>
> John
>
>>
>> Best,
>> Josiah
next prev parent reply other threads:[~2014-02-02 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 21:33 Assistance with patching instructions on Worg John Hendy
2014-01-31 21:50 ` 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 [this message]
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
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=CA+M2ft86X_4t6eEX-W59fXT9H-5hEfm6+Z-VyGaQMLjBmW2bAQ@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jschwab@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).