On 5/29/12 8:43 PM, Rob Weir wrote:
Would it be too much additional overhead if we all agreed to track
patch authors, reviewers, bug authors, etc., in Subversion memo's in a
semi-structured way?
I'm thinking of what the Subversion project does, mainly using 4
possible fields in the check in
Good suggestion to me! Others members could comment what else fields are
needed.
Related topic is, we should set up such guidelines and put it to our wiki,
eg. coding guidelines, unit test report format, defect report format...some
we may already have...
Helen
2012/5/30 Rob Weir
Hi,
On 29.05.2012 20:43, Rob Weir wrote:
Would it be too much additional overhead if we all agreed to track
patch authors, reviewers, bug authors, etc., in Subversion memo's in a
semi-structured way?
I'm thinking of what the Subversion project does, mainly using 4
possible fields in the check
Hi Rob, *
On Tue, May 29, 2012 at 02:43:10PM -0400, Rob Weir wrote:
Would it be too much additional overhead if we all agreed to track
patch authors, reviewers, bug authors, etc., in Subversion memo's in a
semi-structured way?
I'm thinking of what the Subversion project does, mainly using 4
Yue Helen wrote on Wed, May 30, 2012 at 15:02:25 +0800:
Good suggestion to me! Others members could comment what else fields are
needed.
Tested by:
We've used it a few times; I'm not sure the script looks for it.
2012/5/30 Rob Weir robw...@apache.org
Patch by:
Suggested by:
Found
Would it be too much additional overhead if we all agreed to track
patch authors, reviewers, bug authors, etc., in Subversion memo's in a
semi-structured way?
I'm thinking of what the Subversion project does, mainly using 4
possible fields in the check in memo:
Patch by:
Suggested by:
Found by:
On Tue, May 29, 2012 at 11:43 AM, Rob Weir robw...@apache.org wrote:
Would it be too much additional overhead if we all agreed to track
patch authors, reviewers, bug authors, etc., in Subversion memo's in a
semi-structured way?
I'm thinking of what the Subversion project does, mainly using 4
