simon.sinister at sbcglobal
May 27, 2012, 2:42 PM
Post #4 of 4
Thank you Mike, for providing the 'git diff origin/master HEAD >
example (which I used to submit my patch), and thank you Karl for the
example. I'll try that next time.
On 05/27/2012 04:11 AM, Karl Dietz wrote:
> Hi Steve,
> On 24.05.2012 05:30, Michael T. Dean wrote:
>> On 05/23/2012 10:40 PM, Steve E wrote:
>>> I have a solution for a ticket which already exists.
>>> I've implemented the fix in my view. I've run 'git add' and 'git
>>> commit -v', but
>>> now the Myth development documentation has left me hanging. What
>>> is the next step?
>>> Please provide me some guidance on how to proceed.
>> You can use:
>> git diff origin/master HEAD >
>> to create a patch, which you can attach to the ticket. (Assuming you
>> made the changes in the master branch.)
>> Alternatively, you can create a pull request (
>> http://help.github.com/send-pull-requests/ ), and then add a comment to
>> the ticket that references the pull request you've submitted.
> I do it like this.
> I "git pull" master, then move my changes forward to the latest master
> with "git rebase origin" and create patches with "git format-patch
> that allows me to shuffle around my patches with "git rebase -i origin"
> and recreate a set of all my patches
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
mythtv-dev mailing list
mythtv-dev [at] mythtv