On 10/12/13 15:05, Jorge Cardoso Leitão wrote: > Hi there. > > I'm having difficulties to commit to Pyglet.
See: http://pyglet.org/contribute.html (I know you have checked it, but just for the record) > 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 know it's confusing, but we're not using GitHub but Google Code. Why not GitHub? That's a discussion for a different occasion I think; I wouldn't like to change things infrastructure wise when we have other things that require our attention. There's not pull request, you make a ticket with your changes: either link to the repo/commit or a patch. > 2. How can I pull the latest version of pyglet rep to my local machine > so that I can update my remote rep? The way hg works is different than git. In git you branch for a feature, in hg you clone per feature; so you don't upgrade your clone unless you want to "rebase" your changes before opening the issue asking for merge. I'm an hg newbie myself, I don't want to Google for an answer so I rather let any other list member to reply this part. > 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. The website explains what to do, but there's always room for improvement. Basically: open an ticket in the issue tracker describing your change and link the clone/commit. A project member will review your commit providing feedback and eventually it will be merged into the official repository. (Alternatively you can also create a patch of your changes and attach it to the ticket: hg diff [-r rev] > name-of-the-patch.patch) > 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. AFAIK we don't use Bitbuket. > This brings the question: who commits to Pyglet besides those with > commit privileges and how do they(you?) do it? > You have done the right thing: ask in the mailing list! As I said, the workflow would be: clone, hack, commit, merge. I don't maintain a public clones though as I have a local clone of the main repo that I keep clean. But I'm an hg newbie, so please... feedback/comments are very welcome! Regards, Juan -- Juan J. Martinez Software Developer, MEMSET mail: [email protected] web: http://www.memset.com/ Memset Ltd., registration number 4504980. Building 87, Dunsfold Park, Stovolds Hill, Cranleigh, Surrey GU6 8TB, UK. -- 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.
