From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: :cache documentation patch
Date: Wed, 05 Jan 2011 21:47:25 -0700 [thread overview]
Message-ID: <878vyyfxgo.fsf@gmail.com> (raw)
In-Reply-To: B87FE7FD-DF2E-43E2-BCCA-C42558DE773E@tsdye.com
Hi Tom,
Yes, the commit is important, this method actually shares all of your
commit, including the author information and the commit message.
I do this outside of magit, I tend to go to the magit buffer to make
sure everything looks ok, then do M-! and type in the command line
manually. I'm not sure what the magit way of doing this would be, but
the "D" method you described doesn't generate the same type of output
file as does git format-patch.
Thanks -- Eric
"Thomas S. Dye" <tsd@tsdye.com> writes:
> Hi Eric,
>
> Will do. The earlier patch was made with magit. I used the d
> command, Diff working tree, then saved the output to the file I sent.
>
> If I understand correctly, the missing step was the commit. I should
> be able to follow a commit with the D command in magit, starting at
> HEAD~1 and ending with HEAD. Then save the resulting buffer to
> foo.patch, right?
>
> Or, is it better to do this outside magit so the results don't pass
> through an emacs buffer on their way to disk?
>
> All the best,
> Tom
>
> On Jan 5, 2011, at 6:27 AM, 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
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
2011-01-05 18:32 ` Thomas S. Dye
2011-01-06 4:47 ` Eric Schulte [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vyyfxgo.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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 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.