From: Jens Axboe <qemu@kernel.dk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] proper support of FLUSH_CACHE and FLUSH_CACHE_EXT
Date: Thu, 5 Jan 2006 09:14:19 +0100 [thread overview]
Message-ID: <20060105081417.GQ3389@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0601042205590.5157@wbgn013.biozentrum.uni-wuerzburg.de>
On Wed, Jan 04 2006, Johannes Schindelin wrote:
> Hi,
>
> On Wed, 4 Jan 2006, Jens Axboe wrote:
>
> > 1.0.GIT
>
> Using git for QEmu development? Welcome to the club. ;-)
Yes I just imported the repo into git, cvs isn't really my cup of tea
and it isn't very handy for patch series. git isn't very tailored for
that as well, but at least it allows me to just do a 'format-patch'
against the old master and get the patch series. And with a devel
branch, it's pretty easy to pull the new updates and rebase the devel
branch as needed.
Are you using a persistent git repo for qemu (ie continually importing
new changes)? I've considered setting one up :-)
> Regarding your patches: as far as I understand them, I like 'em.
Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2006-01-05 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 12:12 [Qemu-devel] [PATCH 0/3] qemu ide updates Jens Axboe
2006-01-04 12:12 ` [Qemu-devel] [PATCH 1/3] ide id updates Jens Axboe
2006-01-04 12:13 ` [Qemu-devel] [PATCH 2/3] ide lba48 support Jens Axboe
2006-02-01 22:34 ` Fabrice Bellard
2006-02-02 9:53 ` Jens Axboe
2006-01-04 12:16 ` [Qemu-devel] [PATCH 3/3] proper support of FLUSH_CACHE and FLUSH_CACHE_EXT Jens Axboe
2006-01-04 21:07 ` Johannes Schindelin
2006-01-05 8:14 ` Jens Axboe [this message]
2006-01-05 9:18 ` Jens Axboe
2006-01-05 13:25 ` Johannes Schindelin
2006-01-05 18:07 ` Jens Axboe
2006-01-05 13:11 ` Johannes Schindelin
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=20060105081417.GQ3389@suse.de \
--to=qemu@kernel.dk \
--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).