emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: :cache documentation patch
Date: Wed, 5 Jan 2011 21:45:10 -1000	[thread overview]
Message-ID: <B6C3B069-DD97-4AE7-9162-D5A041F290D5@tsdye.com> (raw)
In-Reply-To: <878vyyfxgo.fsf@gmail.com>

Hi Eric,

Thanks for the detailed instructions.  I'll follow this path next time.

All the best,
Tom

On Jan 5, 2011, at 6:47 PM, Eric Schulte wrote:

> 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

      reply	other threads:[~2011-01-06  7:46 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
2011-01-06  7:45       ` Thomas S. Dye [this message]

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=B6C3B069-DD97-4AE7-9162-D5A041F290D5@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).