Certainly.
For something like this where the bug is that the regressions don't run
to completion,
I would have 4 different checkins each referencing the same jira issue then?
I started building different jira issues for each "bug", but I ended up
just duping them
to the general "regressions do not run to completion" bug as the
problems were all
trivial and it didn't seem to help tracking to make 4 different bugs.
I would then attach the 4 different revision numbers to the jira issue
when I marked it 'fixed'.
Is that reasonable?
john
On 12/9/2009 9:00 AM, Paul Querna wrote:
On Tue, Dec 8, 2009 at 7:16 AM,<[email protected]> wrote:
Author: jplevyak
Date: Tue Dec 8 15:16:13 2009
New Revision: 888434
URL: http://svn.apache.org/viewvc?rev=888434&view=rev
Log:
TS-73: seg fault during regressions (traffic_server -R1) fix:
double delete in ParentSelection.cc
uninitialized global in CongestionDB.cc
debugging code used instead of real regression in Cache.cc
forgotten set of new UnixNetVConnection::closed to 0 on acceptEvent in
UnixNetVConnection.cc
I know we all get coding and sometimes make a slew of changes when we
start trying to fix one thing, but if possible please try to do one
functional change with a single commit, it makes following along much
easier, and enable log/blame VC history of single files to be much
clearer.
Thanks,
Paul
