[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: weekly report for 2009-06-08~2009-06-13

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 15 Jun 2009 12:52:47 +0100

On Mon, Jun 15, 2009 at 10:06:18AM +0800, yellow.flying wrote:
> Hey Stefan,
> This week:
> 1. write patch for commit_tests.py
> and some conclusions:
> 1. create patches from the working copy root.
> 2. always keep comments in sync with code you are changing.

I'm learning things, too:

2a. always keep code in sync with comments you are changing
2b. don't commit broken code

I failed both rules 2a and 2b this week :(

> 3. need to mention *every* hunk of the patch in log message, describing the change made by the hunk.
> 4. always make sure you understand why a test is failing.

I also didn't do 4. properly the first time around...

And also:

5. If the mentor is being too hasty when trying to give advice,
   the advice won't be correct and everyone will be confused.
   Mentors should try _not_ to confuse themselves and gsoc students.

> next week:
> 1. write code.

Yeah, I'm looking forward to that :)

Received on 2009-06-15 13:53:13 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.