When you do merges (and not rebases) your bisect and blame also conk out.
http://mettadore.com/analysis/a-simple-git-rebase-workflow-explained/
On Wed, May 15, 2013 at 10:39:11AM -0700, Alena Prokharchyk wrote:
> Fixed this particular problem to unblock the QA and dev. It should have
> been if (!
Fixed this particular problem to unblock the QA and dev. It should have
been if (!canHandleLbRules). The problem was introduced by my merge from
internalLb branch done with the single squashed commit
(2660a6b7a7f226ab757d2175222db62571813120) on May 9th. Not sure why
Nitin's merge from May 11th ove
Git blame shows un-intended change due
to c11dbad9c9ba7a876243ec02e90215906cfd9115. Nitin, can you see why your
merge brought these changes? Please figure root cause, its possible other
files got affected as well.
On Wed, May 15, 2013 at 6:17 PM, Rajesh Battala
wrote:
> Hi,
>
> I was not able to
Hi,
I was not able to create LB rule on Netscaler device when Netscaler device is
my LB provider in my network offering.
I debugged and figured out that, in applyLBRules method
if (canHandleLbRules(rules)) {
return false;
}
Even the method canHandleLbRules is return
