There''s actually an additional step of creating a branch for your
changes
and sending the pull request from there rather then just using your master.
Makes it far easier for the changes to be merged back into trunk.
There''s a page on the wiki here:
https://github.com/mapstraction/mxn/wiki/Contributing
Cheers,
Derek
On 14 July 2011 02:32, Adam DuVander <mapstraction at duvander.com> wrote:
> Hi all,
>
> Derek uploaded a new Mapstraction build today:
> https://github.com/mapstraction/mxn/downloads
>
> This made me revisit an email to this list from Vito Tafuni about a year
> ago. In it, Vito spelled out the steps to contribute to Mapstraction:
>
> 1. make a fork of the project on github
> 2. git clone git-repos-address folder
> 3. cd folder
> 4. make your changes
> 5. git status - give info about changes made on files
> 6. git add . or git add filename1 filename2 ... - only if you have added
> new files
> 7. git commit or git commit filename - the latter version of the command
> let you comment the changes on a single file
> 8. git push - send changes to the repo you''ve forked
> 9. ask for a pull on github
>
> _______________________________________________
> Mapstraction mailing list
> Mapstraction at lists.mapstraction.com
> http://lists.mapstraction.com/listinfo.cgi/mapstraction-mapstraction.com
>
>
--
Derek Fowler
m. +44 (0) 7966 512 369
e. dezfowler at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.mapstraction.com/pipermail/mapstraction-mapstraction.com/attachments/20110714/2df189b7/attachment.htm>