From: Damien Mascord <tusker@tusker.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CVS snapshots
Date: Wed, 30 Jun 2004 15:00:19 +0800 [thread overview]
Message-ID: <40E26503.90703@tusker.org> (raw)
In-Reply-To: <40B3217E.1000900@witch.dyndns.org>
Hi Hetz,
Would it be possible to automate a static build of the CVS snapshot ?
I have issues compiling qemu due to the lack of static libraries on my
system (source based distro - sourcemage).
Obviously, no point including failed builds, but that would be an easy
shell error check.
Damien
Hetz Ben Hamo wrote:
> Hi People,
>
> As a person who had this "pleasure" of unable to access the CVS from
> work, I had decided to start doing a nightly snapshot (source, not build)..
>
> Every night at 23:40 (GMT +2) there will be created a snapshot of QEMU
> cvs and will be located at: http://dad-answers.com/qemu/
>
> There will be only 1 snapshot available each day (due to bandwidth and
> disk space issues)..
>
> Please note, that the "qemu" directory has been renamed to match the
> tarball name, so people will not accidently extract the tarball on an
> already "qemu" directory.
>
> Finally - a small question: does anyone knows about a recommended (free)
> tool for Windows to extract tar.bz2 without going to same route twice
> using programs like winzip and winrar?
>
> Thanks,
> Hetz
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
--
Damien Mascord (tusker at tusker dot org)
GPG key 2CB181BE / 93B2 EF21 0C7C F022 F467 7966 219E 92B3 2CB1 81BE
prev parent reply other threads:[~2004-06-30 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 10:35 [Qemu-devel] CVS snapshots Hetz Ben Hamo
2004-05-25 11:16 ` Jason Gress
2004-05-25 11:25 ` Rudi Lippert
2004-05-25 16:47 ` John R. Hogerhuis
2004-05-26 17:24 ` Emre Ersin
2004-06-30 7:00 ` Damien Mascord [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=40E26503.90703@tusker.org \
--to=tusker@tusker.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).