On Tuesday, December 10, 2013 6:05:47 PM UTC+3, Jorge Cardoso Leitão wrote: > > Hi there. > > I'm having difficulties to commit to Pyglet. > > I first cloned it using the googlecode interface. Second I clone my remote > rep to my local machine. Then, I modify, commit, and push the commit back > to my remote rep in google. Now: > > 1. How can I "pull request"? >
I guess you mean "create pull request"? Google Code can not do this automatically, but you can create an issue and specify the URL of your repository to pull from. > 2. How can I pull the latest version of pyglet rep to my local machine so > that I can update my remote rep? > Well, when you clone, you get the copy. When you do 'hg pull -u', you get the latest copy. Then you do 'hg push your_remote_rep' to update. > Maybe it is because I'm used to GitHub, but I'm not finding the workflow > explained anywhere. I'm sorry If I'm not familiar with diffs and patches, > but I never had to use them. > > I looked at a pyglet rep in BitBucket<https://bitbucket.org/irskep/pyglet> > but > the activity is none so I suspect it is not used to commit. > You can clone from https://bitbucket.org/rirror/pyglet/overview it is auto synced. > This brings the question: who commits to Pyglet besides those with commit > privileges and how do they(you?) do it? > Not me. -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/groups/opt_out.
