Using git is more than a little different way of doing business for me.
My usual way to create and apply a patch is to rebuild a src.rpm. This
way I have a lot less changes of screwing something up because of ignorance.
It it a little while but I finally cloned a copy of libvirt.git. I
On 09/06/2012 09:59 AM, Gene Czarcinski wrote:
Using git is more than a little different way of doing business for me.
My usual way to create and apply a patch is to rebuild a src.rpm. This
way I have a lot less changes of screwing something up because of
ignorance.
It it a little while
On Thu, Sep 06, 2012 at 11:59:10AM -0400, Gene Czarcinski wrote:
Using git is more than a little different way of doing business for
me. My usual way to create and apply a patch is to rebuild a
src.rpm. This way I have a lot less changes of screwing something
up because of ignorance.
It
On 09/06/2012 11:59 AM, Gene Czarcinski wrote:
Using git is more than a little different way of doing business for
me. My usual way to create and apply a patch is to rebuild a
src.rpm. This way I have a lot less changes of screwing something up
because of ignorance.
My experience is the
On 09/06/2012 12:53 PM, Daniel P. Berrange wrote:
FYI in case you don't already know, you can also run libvirt builds
directly from the source tree, rather than needing to run 'make intsall'
or install an updated RPM every time. my usual way of working is to
just stop the libvirtd process
Rather than cluttering up the mailing list, I am going to combine the
helpful replies into a single response. I am going to edit this to
reduce clutter.
On 09/06/2012 01:26 PM, Laine Stump wrote:
On 09/06/2012 11:59 AM, Gene Czarcinski wrote:
Using git is more than a little different way of
