From: "Eric Schulte" <schulte.eric@gmail.com>
To: mail@christianmoe.com
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: :cache documentation patch
Date: Wed, 05 Jan 2011 21:49:02 -0700 [thread overview]
Message-ID: <87fwt6fxgv.fsf@gmail.com> (raw)
In-Reply-To: 4D24B24D.8070302@christianmoe.com
Hi Christian,
It's probably safer to stick with the worg guidelines than to follow my
advice :)
In the specific case of Tom's patches, I prefer the "git format-patch"
approach I described because it allows Tom to write the commit message,
and all I have to do is run a single command and the patch is applied.
Cheers -- Eric
Christian Moe <mail@christianmoe.com> writes:
> Hi, Eric,
>
> Does this process produce the same output as the one described here:
> http://orgmode.org/worg/org-contribute.html#sec-3
>
> Or is this a better way, and should the worg documentation be updated?
>
> I don't understand git, and depend on documentation to help me do the
> right thing.
>
> Yours,
> Christian
>
> On 1/5/11 5:27 PM, Eric Schulte wrote:
>> Applied, Thanks -- Eric
>>
>> p.s. would you mind submitting git formatted patches for these sort of
>> updates in the future? It greatly simplifies the process of
>> applying the patch. The process for creating a git formatted patch
>> is as follows...
>>
>> 1. commit your changes to your local copy of the org-mode
>> repository
>> 2. run the following command to wrap up the latest commit on your
>> local copy of the repository into a file which can be attached
>> to email messages
>>
>> git format-patch -o ~/Desktop/ HEAD~1
>>
>> after the command finished you will notice a new file on your
>> Desktop with a name like 0001-commit-message-stuff.patch
>>
>> Thanks Again -- Eric
>>
>> "Thomas S. Dye"<tsd@tsdye.com> writes:
>>
>>> Aloha all,
>>>
>>> The attached patch documents the behavior of the :cache header argument.
>>>
>>> All the best,
>>> Tom
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> 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:[~2011-01-06 4:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 21:33 :cache documentation patch Thomas S. Dye
2011-01-05 16:27 ` Eric Schulte
2011-01-05 18:02 ` Christian Moe
2011-01-06 4:49 ` Eric Schulte [this message]
2011-01-05 18:32 ` Thomas S. Dye
2011-01-06 4:47 ` Eric Schulte
2011-01-06 7:45 ` Thomas S. Dye
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=87fwt6fxgv.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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).