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
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
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
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 an
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,
Ch
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
