search for: copyedit

...so the tests are adjusted > > > accordingly. > > > > This patch seems to cause the tests in v2v/ to fail. > > All v2v tests pass for me. Could you please provide the logs to > investigate? Attached. The patches are fine to push as long as: - replace 5/5 with my copyedited version - fix the test failure Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html

...Balance Around Your Mongrels'' Health * Quick & Dirty Search * Use Fixtures For Canned Datasets * Cheap & Easy Caching (requires Edge Rails) * Drive a Feature with Integration Tests * Write Domain-Specific RSpec Matchers * Use DTrace for Profiling The book will go into production (copyedit, layout, etc.) very soon, so if you notice any problems and things that could use a bit more clarification, I''d really appreciate it if you''d file errata using the link on the book''s page. I''ll work ''em all off for the final revision. Thanks to all the...

Can you explain how to revert for someone who is a 2 on a git scale of 0 to 10? At 9/22/2020 03:51 PM, Arthur Eubanks wrote: >Yes, push whatever is needed to fix the build if the fix is fairly simple (else revert and get an LGTM with the fix). > >Next time I'd recommend creating and pushing a revert first if you can't quickly figure out the issue.

...>? ???> Twitter, I wonder if preserving the recycling behavior test is > longer than >? ???> yes, no, but making the case where > >? ???> length( test ) < max(length( yes ), length( no )) > >? ???> would simplify usage for userRs in a useful way. > That was a copyediting bug on my part, it seems I hit send with my message only half-edited/proofread. Apologies. That should have said that making the case where test is the one that will be recycled (because it is shorter than either yes or no) an error. My claim is that the fact that test itself can be recycled,...

The decision on which device type to use for disks, network and video cards on output used to be taken deep inside the converting functions. This is not always desirable. In particular, there are scenarios when this decision is made before the convertion takes place. E.g. in in-place mode, the decisions are taken and the output VM configuration is created outside of v2v tool. This patchset

...st is >> longer than >> ? ???> yes, no, but making the case where >> >> ? ???> length( test ) < max(length( yes ), length( no )) >> >> ? ???> would simplify usage for userRs in a useful way. >> > That was a copyediting bug on my part, it seems I hit send with my message > only half-edited/proofread. Apologies. > That should have said that making the case where test is the one that will > be recycled (because it is shorter than either yes or no) an error. My > claim is that the fact...

All, Martin: Thanks for this and all the other things you are doing to both drive R forward and engage more with the community about things like this. Apologies for missing this discussion the first time it came around and if anything here has already been brought up, but I wonder what exactly you mean when you want recycling behavior. Specifically, based on an unrelated discussion with Henrik