qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <anthony@codemonkey.ws>
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: Thu, 22 Sep 2011 20:27:28 +0200	[thread overview]
Message-ID: <4E7B7E10.5020905@mail.berlios.de> (raw)
In-Reply-To: <4E7B4E88.4070700@codemonkey.ws>

Am 22.09.2011 17:04, schrieb Anthony Liguori:
> On 09/22/2011 09:55 AM, Jan Kiszka wrote:
>>
>> Does Savannah support user cronjobs? Then you could auto-pull qemu.org's
>> public tree once in a while.
>
> Not as far as I can tell.
>
> Regards,
>
> Anthony Liguori


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.

If this works, it would be a better solution than removing the repo.
I don't have project access to a savannah project, otherwise I
could try it myself.

Regards,

Stefan

  reply	other threads:[~2011-09-22 18:27 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           ` Stefan Weil [this message]
2011-09-23 11:53             ` [Qemu-devel] stale savannah git repo Andreas Schwab
2011-09-23 16:09               ` Stefan Weil

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=4E7B7E10.5020905@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=bradh@frogmouth.net \
    --cc=jan.kiszka@siemens.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).