[GSOC 2014] - Yangmin's current work

yangmin zhu zym0017d at gmail.com
Tue May 20 15:59:22 UTC 2014

On Mon, May 19, 2014 at 6:15 PM, Philippe Ombredanne
<pombredanne at nexb.com> wrote:
> On Sun, May 18, 2014 at 6:24 PM, yangmin zhu <zym0017d at gmail.com> wrote:
> 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.

I had used git to clone back the strace code from sourceforge few days
ago. And then I copied these code
to somewhere else in my local computer and start to work in the local
directory. This is some kind same to
download from a snapshot because I lost the git data by just copying
the source code.
I will make changes to my repository and this time I will start 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.

Thank you for your advise about the workflow! I am really new to open
source project
and feel some kind lost about how the open source development work.
I found the strace code changing every week. And I will merge the
latest strace code
to my github regularly to keep up to date.
I am going to do some cleaning on my github. I tried some git commands
and it seems
brought some small problems to the repository. And I need to study
more about git and
the source control things.

> 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.

Yes, I realized It would be better to make it clear what code I
accutually wrote.
In my strace_GSOC2014 repository, I had made a tag v1.0 to the base strace code.


More information about the Strace-devel mailing list