From: Stefan Weil <weil@mail.berlios.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Brad Hards <bradh@frogmouth.net>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] stale savannah git repo
Date: Fri, 23 Sep 2011 18:09:48 +0200 [thread overview]
Message-ID: <4E7CAF4C.7020206@mail.berlios.de> (raw)
In-Reply-To: <m2wrcztqym.fsf@igel.home>
Am 23.09.2011 13:53, schrieb Andreas Schwab:
> Stefan Weil<weil@mail.berlios.de> writes:
>
>> Maybe this works:
>>
>> * Get login account for savannah:
>> http://www.gnu.org/software/README.accounts.html
>>
>> * Upload your public ssh key to savannah.
>>
>> * Run a cron job on qemu.org:
>> ssh to savannah or fencepost.gnu.org and update the git repo.
> You don't need a fencepost account for that, just commit access to the
> qemu repo at savannah.
>
> (In any case the private ssh key needs to be accessible to the cron
> job.)
>
> Andreas.
... it can be any private key, so it's possible to create an
account "savannah" on qemu.org (without login access)
which runs the cron job.
prev parent reply other threads:[~2011-09-23 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 10:14 [Qemu-devel] stale savannah git repo (was: Re: KVM call agenda for April 05) Peter Maydell
2011-06-14 13:24 ` Anthony Liguori
2011-09-22 14:20 ` Peter Maydell
2011-09-22 14:34 ` Anthony Liguori
2011-09-22 14:37 ` Peter Maydell
2011-09-22 14:55 ` Jan Kiszka
2011-09-22 15:04 ` Anthony Liguori
2011-09-22 18:27 ` [Qemu-devel] stale savannah git repo Stefan Weil
2011-09-23 11:53 ` Andreas Schwab
2011-09-23 16:09 ` Stefan Weil [this message]
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=4E7CAF4C.7020206@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=agraf@suse.de \
--cc=bradh@frogmouth.net \
--cc=jan.kiszka@siemens.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=schwab@linux-m68k.org \
--cc=stefanha@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.