Jan Kiszka wrote:
I'm thinking how to do it. pushing requires an ssh key, and I don't
want to leave one around without a passphrase, which would be required
by a cron job.
Any ideas?
Local commit hook that triggers the push (and ask you for the phrase
interactively)? But that also d
Avi Kivity wrote:
> Jan Kiszka wrote:
>
>
>
>>> Maybe I need to have a script
>>> push my master branch somewhere, so you don't duplicate my work
>>> needlessly.
>>>
>>>
>>
>> That would be highly appreciated.
>>
>
> I'm thinking how to do it. pushing requires an ssh key, and I don't
Jan Kiszka wrote:
Maybe I need to have a script
push my master branch somewhere, so you don't duplicate my work needlessly.
That would be highly appreciated.
I'm thinking how to do it. pushing requires an ssh key, and I don't
want to leave one around without a passphrase, which
Avi Kivity wrote:
> Jan Kiszka wrote:
>> Various fixes that were required to build against a 2.6.18 kernel, but
>> some affect newer kernels, too:
>>
>>- replacements for uaccess.h and relay.h
>> - flush_work compat wrapper
>> - fix msi_enabled hack
>> - hack eventfd.c for INIT_WORK
>>
>
On (Tue) May 26 2009 [10:49:35], Avi Kivity wrote:
> I had these two already, but not pushed. Maybe I need to have a script
> push my master branch somewhere, so you don't duplicate my work
> needlessly.
A 'next' branch that's the real bleeding-edge, while the patches get
tested and master get
Jan Kiszka wrote:
Various fixes that were required to build against a 2.6.18 kernel, but
some affect newer kernels, too:
- replacements for uaccess.h and relay.h
- flush_work compat wrapper
- fix msi_enabled hack
- hack eventfd.c for INIT_WORK
Please split into separate patches.
