addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

git and patch protocols...

From: Jon S.
Sent on: Wednesday, September 9, 2009 8:15 AM
Hi... I've forked cucumber and patched a couple of bugs.  Now I want to submit them and they (Aslak) wants a diff. Also, I  forked[masked] and now they're now at 0.3.99.
So.... with apologies to Lewis Carroll, I've a portmanteau question before I dive into the manuals:
1. I'm guessing that I should update my fork with the latest version before I pull the diff... right?
2. I can do a 'normal' diff on my machine, but is there a preferred way using git?
3. How careful do I need to be about which version the diff is against... does a git diff make that clear or is there some approach for spelling this out beyond just a note in the post?
4. In general, is there an accepted protocol for submitting patches? (For cucumber, they've got a lighthouse app and all submittals are through their ticketing system as opposed to direct upload as I saw was done for merb.)
Thanks for your thoughts/suggestions...jon

Jon Seidel, CMC��
EDP Consulting, Inc. / /
Business: That's what 'Technology' Means! - Since 1979

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy