I have a large series of patches I'm about to post for
review. I'm breaking them up into a set of smaller series
so each of them can be reviewed fairly independently.
Each group of patches will normally have some logical
connection to each other, though that connection might
be somewhat tenuous.
I have created a new branch for-review-1 that addresses all review
comments received so far for the commits in the for-review branch.
A number of the patches needed slight changes based on requested
changes to patches earlier in the series.
Over the next few hours I plan to send out a lot of patches
for review. Most of these have been around and under test
for a month or more, and at the time I originally committed
them I wasn't sure how best to get them reviewed.
We decided that sending them all out to the list was a
good way to
On 02/28/2012 06:14 PM, Alex Elder wrote:
Over the next few hours I plan to send out a lot of patches
for review. Most of these have been around and under test
for a month or more, and at the time I originally committed
them I wasn't sure how best to get them reviewed.
We decided that sending
On 02/28/2012 06:14 PM, Alex Elder wrote:
Over the next few hours I plan to send out a lot of patches
for review. Most of these have been around and under test
for a month or more, and at the time I originally committed
them I wasn't sure how best to get them reviewed.
We decided that sending
