- Original Message -
> From: "Zdenek Styblik"
> On Thu, Aug 29, 2013 at 1:38 PM, Liebig, Holger
> wrote:
.snip.
> > I know it's late and I understand your concerns. My (lame) excuse is that
> > CVS is not working behind our corporate proxy e.g. and I was waiting for a
> > current tarball
On Thu, Aug 29, 2013 at 1:38 PM, Liebig, Holger
wrote:
[...]
>
> Zdenek,
> I know it's late and I understand your concerns. My (lame) excuse is that CVS
> is not working behind our corporate proxy e.g. and I was waiting for a
> current tarball to show up on the sourceforge project page.
Hehe, t
> On Thu, Aug 29, 2013 at 9:37 AM, Liebig, Holger
> wrote:
> > Jim,
> > any chance to include my small patch from 2011 regarding SOL input buffer
> size?
...
>
> Holger,
>
> release of 1.8.13 was announced well ahead, there was plenty of time etc.
> etc. No, no more fixes into 1.8.13. It's 28th
On Thu, Aug 29, 2013 at 9:37 AM, Liebig, Holger
wrote:
> Jim,
> any chance to include my small patch from 2011 regarding SOL input buffer
> size?
> The problem is related when a user is using copy&paste and is pasting large
> blocks of text (>255) into the ipmitool SOL session at once. Ipmitool
Jim,
any chance to include my small patch from 2011 regarding SOL input buffer size?
The problem is related when a user is using copy&paste and is pasting large
blocks of text (>255) into the ipmitool SOL session at once. Ipmitool is using
the reported SOL max inbound payload size for the alloca
