Arnd Bergmann wrote:
On Tuesday 20 March 2007, Avi Kivity wrote:
I find using a patch queue useful though for submitting things
upstream. A good example is our QEMU changes. It's a real pain to
break apart the SVN history into individual patches.
Why not just extract diffs
Avi,
Should libc and a kernel be put into the same repository? As far as I
have seen, the pain of migrating kvm into git was caused by interface
incompatibility between libkvm and kvm due to rapid interface flux. I
think the interface should be well-defined, and boiled down, to the
point that
On Tue, Mar 20, 2007 at 8:13 AM, in message [EMAIL PROTECTED],
Avi Kivity [EMAIL PROTECTED] wrote:
Managing userspace in subversion and the kernel in git is proving to be
quite a pain. Branches have to be maintained in parallel, tagging is
awkward, and bisection is fairly impossible.
On Tue, Mar 20, 2007 at 8:37 AM, in message [EMAIL PROTECTED],
Avi Kivity [EMAIL PROTECTED] wrote:
Gregory Haskins wrote:
Avi Kivity [EMAIL PROTECTED] wrote:
Managing userspace in subversion and the kernel in git is proving to be
quite a pain. Branches have to be maintained in
On Tuesday 20 March 2007, Avi Kivity wrote:
Managing userspace in subversion and the kernel in git is proving to be
quite a pain. Branches have to be maintained in parallel, tagging is
awkward, and bisection is fairly impossible.
What do people think about putting libkvm and qemu into the
Avi Kivity wrote:
Arnd Bergmann wrote:
On Tuesday 20 March 2007, Avi Kivity wrote:
Managing userspace in subversion and the kernel in git is proving to be
quite a pain. Branches have to be maintained in parallel, tagging is
awkward, and bisection is fairly impossible.
What
Arnd Bergmann wrote:
On Tuesday 20 March 2007, Avi Kivity wrote:
How does that work with multiple developers?
You need a set of well-understood rules if more than one person
has commit access to the repository.
The most simple rule would be that everyone just adds patches at
the
Anthony Liguori wrote:
I find using a patch queue useful though for submitting things
upstream. A good example is our QEMU changes. It's a real pain to
break apart the SVN history into individual patches.
Why not just extract diffs with 'svn diff'? That's what I did/do.
I tend to keep
On Tuesday 20 March 2007, Avi Kivity wrote:
I find using a patch queue useful though for submitting things
upstream. A good example is our QEMU changes. It's a real pain to
break apart the SVN history into individual patches.
Why not just extract diffs with 'svn diff'? That's what I
