On 4 May 2016 at 14:30, Simon Glass wrote:
> On 4 May 2016 at 14:27, Tom Rini wrote:
>> On Wed, May 04, 2016 at 01:30:47PM -0600, Simon Glass wrote:
>>> Hi Tom,
>>>
>>> On 4 May 2016 at 13:09, Stephen Warren wrote:
>>> > On 05/04/2016 12:58 PM, Tom Rini wrote:
>>> >>
>>> >> On Wed, May 04, 2016
On 4 May 2016 at 14:27, Tom Rini wrote:
> On Wed, May 04, 2016 at 01:30:47PM -0600, Simon Glass wrote:
>> Hi Tom,
>>
>> On 4 May 2016 at 13:09, Stephen Warren wrote:
>> > On 05/04/2016 12:58 PM, Tom Rini wrote:
>> >>
>> >> On Wed, May 04, 2016 at 12:55:15PM -0600, Stephen Warren wrote:
>> >>>
>>
On Wed, May 04, 2016 at 01:30:47PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On 4 May 2016 at 13:09, Stephen Warren wrote:
> > On 05/04/2016 12:58 PM, Tom Rini wrote:
> >>
> >> On Wed, May 04, 2016 at 12:55:15PM -0600, Stephen Warren wrote:
> >>>
> >>> On 04/11/2016 10:48 AM, Stephen Warren wrote:
Hi Tom,
On 4 May 2016 at 13:09, Stephen Warren wrote:
> On 05/04/2016 12:58 PM, Tom Rini wrote:
>>
>> On Wed, May 04, 2016 at 12:55:15PM -0600, Stephen Warren wrote:
>>>
>>> On 04/11/2016 10:48 AM, Stephen Warren wrote:
From: Stephen Warren
One use-case for buildman is to con
On 05/04/2016 12:58 PM, Tom Rini wrote:
On Wed, May 04, 2016 at 12:55:15PM -0600, Stephen Warren wrote:
On 04/11/2016 10:48 AM, Stephen Warren wrote:
From: Stephen Warren
One use-case for buildman is to continually run it interactively after
each small step in a large refactoring operation. T
On Wed, May 04, 2016 at 12:55:15PM -0600, Stephen Warren wrote:
> On 04/11/2016 10:48 AM, Stephen Warren wrote:
> >From: Stephen Warren
> >
> >One use-case for buildman is to continually run it interactively after
> >each small step in a large refactoring operation. This gives more
> >immediate fe
On 04/11/2016 10:48 AM, Stephen Warren wrote:
From: Stephen Warren
One use-case for buildman is to continually run it interactively after
each small step in a large refactoring operation. This gives more
immediate feedback than making a number of commits and then going back and
testing them. Fo
Hi,
On 25 April 2016 at 10:41, Stephen Warren wrote:
>
> On 04/11/2016 10:48 AM, Stephen Warren wrote:
>>
>> From: Stephen Warren
>>
>> One use-case for buildman is to continually run it interactively after
>> each small step in a large refactoring operation. This gives more
>> immediate feedbac
On 04/11/2016 10:48 AM, Stephen Warren wrote:
From: Stephen Warren
One use-case for buildman is to continually run it interactively after
each small step in a large refactoring operation. This gives more
immediate feedback than making a number of commits and then going back and
testing them. Fo
From: Stephen Warren
One use-case for buildman is to continually run it interactively after
each small step in a large refactoring operation. This gives more
immediate feedback than making a number of commits and then going back and
testing them. For this to work well, buildman needs to be extrem
10 matches
Mail list logo