From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm-kmod: Various compat fixes for older kernels
Date: Tue, 26 May 2009 11:22:04 +0200 [thread overview]
Message-ID: <4A1BB4BC.8030307@siemens.com> (raw)
In-Reply-To: <4A1BB246.30603@redhat.com>
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
> 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 depends on how frequent you would like to
publish the tree.
Jan
next prev parent reply other threads:[~2009-05-26 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 7:06 [PATCH] kvm-kmod: Various compat fixes for older kernels Jan Kiszka
2009-05-26 7:49 ` Avi Kivity
2009-05-26 8:26 ` Amit Shah
2009-05-26 9:01 ` Jan Kiszka
2009-05-26 9:11 ` Avi Kivity
2009-05-26 9:22 ` Jan Kiszka [this message]
2009-05-26 9:30 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A1BB4BC.8030307@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox