On Sun, May 18, 2014 at 6:24 PM, yangmin zhu <zym00...@gmail.com> wrote: > I am now doing all my work on my own github > ( https://github.com/zym0017d/strace_GSOC2014 ) and I am getting > familiar with git.
To ensure that your code can be reviewed and eventually submitted as patches you would need to start from a clone of the strace git repo. You seem to have no history in github and might have started from some snapshot download instead of starting from a clone. Your workflow could be: - start from a complete clone - in your clone branch from master to do your work (eventually creating multiple smaller branches as needed) - rebase and merge frequently (ideally daily or more) from the upstream strace repo to keep up to date - when done with a logical chunk of work, create a patch to submit to the mailing list for review. At the minimum by using a base strace clone, we could comment on your work directly in your github repo, on things like code style and so on. -- Cordially Philippe Ombredanne ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
