[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[libvirt] libvirt.git vs. firewalls [was: [PATCH] qemu_agent: support qemu agent general command]



[I noticed your mailer prefers Shift_JIS encoding; I'm swapping to
UTF-8, as I find it gives a better experience these days, and hope it
isn't causing you grief]

On 07/05/2012 07:29 PM, MATSUDA, Daiki wrote:
> Hi, All.
> 
> Thank you for many comments.
> And I extremely apologize not to use git... My company's network closes
> the almost port and only http via proxy and simple mail are available.

For cloning libvirt.git, that's not a valid excuse.  There is an http
mirror of libvirt.git at http://repo.or.cz/w/libvirt.git, which lags
upstream by less than a day:

git clone http://repo.or.cz/r/libvirt.git

For submitting patches, it is still possible to hook up 'git send-email'
to go through your company mail (although it may be rather interesting
to research what all it will take).  Even if you can't figure out how to
get 'git send-email' working at your employment, at least using 'git
format-patch' against the latest development tree is better than
developing commits against a release tarball.

Or you can use the distributed nature of git in your favor, along with
the existence of sites like repo.or.cz that allow you to create clone
repos that allow http push.  If you do an http push from your work to
your own repo.or.cz clone, then later pull from that repo and use git
send-email from your personal account when you are no longer firewalled,
then you can avoid the restrictions while still minimizing the time
spent outside of work in dealing with the patch submissions.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]