Oh... Thanks for clarifying, Scott... I thought the 'pull' went the other
But I did get my patches formatted into a diff file and attached into the
lighthouse ticket... I'll dig into the guides some more.
From: [address removed] [mailto:[address removed]] On Behalf Of Scott
Sent: Friday, September 11,[masked]:11 AM
To: [address removed]
Subject: Re: [ruby-81] git and patch protocols...
On Fri, Sep 11, 2009 at 10:04 AM, Jon Seidel <[address removed]> wrote:
> FYI, Scott... Unless I completely missed it, the wiki page you
> referenced talks about using the lighthouseapp ticketing system;
> there's no pull doc there and there's no pull option on their github
> page, either, as there is for Merb. Looks like I'll be doing a git
There is this line in the doc: "When you have done that, mention it in your
ticket or send a pull request." I figured "send a pull request"
meant that they prefer that to the 'format-patch' option. I'm not sure what
you mean "there's no pull option on their github page" - to send a pull
request, you go to _your_ fork of their project
(http://github.com...) and you'll see a 'pull request'
button. Hit that button when your fork has changes that you want them to
pull in. If you have a ticket in Lighthouse open, I would mention the
branch you want them to pull from there, too.
Please Note: If you hit "REPLY", your message will be sent to everyone on
this mailing list ([address removed]) http://ruby.meetu... This
message was sent by Scott Chacon ([address removed]) from The East Bay Ruby
To learn more about Scott Chacon, visit his/her member profile:
To unsubscribe or to update your mailing list settings, click here:
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA