Eloy Duran
e.dur****@super*****
Sun Apr 20 03:28:21 JST 2008
Hey Scott, You could indeed send patches by email. If however you're planning on doing more hacking, it might be handier to push your fork to your own account on github.com and send me a pull request. Eloy On 19 apr 2008, at 17:46, Jonathan deWerd wrote: > Apologies if this is a duplicate post. I don't think the other one > got through. Mail refusing to send and locking up, you know how that > works. > > First use "git-add -u" followed by "git-commit" to commit the > changes to your personal copy of the repository. Then, to dump all > your personal commits into a portable form, use "git-format-patch > origin/master -o ~/Desktop". A bunch (1 if that's how many commits > you made) of files will appear on your desktop, and you can mail > them. There are other methods (you could get someone to pull > directly from your repository), but mailing patches has > significantly less voodoo involved :) > > > PS > I haven't used git-format-patch in a while, I may have messed up the > arguments in some subtle way. If the file appears on your desktop, > great, if not, I am sure someone more experienced than I will > correct me before long. > > > On Apr 18, 2008, at 9:11 PM, Scott Thompson wrote: > >> My apologies for needing remedial hand-holding on this. I'm new to >> git and it's got me a bit confused. >> >> I've made my changes in support of require_framework and I'd like to >> submit them now. I'm afraid, however, that after reading a lot of >> documentation on git, I'm not sure how to do that. >> >> I used "git" to clone down a copy of the source. Then I branched the >> code, made my changes in the branch, but I'm unsure how to proceed. >> My git status says something like: >> >> # On branch rst_require_framework >> # Changes to be committed: >> # (use "git reset HEAD <file>..." to unstage) >> # >> # modified: framework/src/objc/BridgeSupport.m >> # modified: framework/src/ruby/osx/objc/oc_import.rb >> # >> # Changed but not updated: >> # (use "git add <file>..." to update what will be committed) >> # >> # modified: framework/RubyCocoa.xcodeproj/project.pbxproj >> # >> [snip -- untracked files left off for brevity] >> >> So the two files I've changed are there in my branch and I'm ready to >> commit them. What's not clear to me is how I make those changes >> available to you guys so you can review them and put them in the >> "real" repository. >> >> My understanding is that when I did the git clone, I got both a >> repository and a working copy. If I commit it should change the >> repository, but how do I forward those changes to the community at >> large? >> >> Scott >> >> _______________________________________________ >> Rubycocoa-devel mailing list >> Rubyc****@lists***** >> http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel > > _______________________________________________ > Rubycocoa-devel mailing list > Rubyc****@lists***** > http://lists.sourceforge.jp/mailman/listinfo/rubycocoa-devel
