On Mon, Jun 3, 2013 at 12:10 PM, Prasanna Santhanam wrote:
> On Fri, May 31, 2013 at 04:58:45AM -0400, David Nalley wrote:
>> On Fri, May 31, 2013 at 2:59 AM, Prasanna Santhanam wrote:
>> > On Thu, May 30, 2013 at 10:51:12AM -0400, David Nalley wrote:
>> >> Hi folks:
>> >>
>> >> I came across an
On Fri, May 31, 2013 at 04:58:45AM -0400, David Nalley wrote:
> On Fri, May 31, 2013 at 2:59 AM, Prasanna Santhanam wrote:
> > On Thu, May 30, 2013 at 10:51:12AM -0400, David Nalley wrote:
> >> Hi folks:
> >>
> >> I came across an interesting problem today, and think it's one that
> >> deserves fi
On Fri, May 31, 2013 at 2:59 AM, Prasanna Santhanam wrote:
> On Thu, May 30, 2013 at 10:51:12AM -0400, David Nalley wrote:
>> Hi folks:
>>
>> I came across an interesting problem today, and think it's one that
>> deserves fixing.
>>
>> I looked at our jenkins config and found that we build package
On Thu, May 30, 2013 at 10:51:12AM -0400, David Nalley wrote:
> Hi folks:
>
> I came across an interesting problem today, and think it's one that
> deserves fixing.
>
> I looked at our jenkins config and found that we build packages in a
> manner that is different from how our documentation tells
Hi folks:
I came across an interesting problem today, and think it's one that
deserves fixing.
I looked at our jenkins config and found that we build packages in a
manner that is different from how our documentation tells users to
build those packages. IMO while there may be more than one way to