BTW what happened to qemu-commit?
It deosn't seem to be working.
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
On Wed, Dec 02, 2009 at 01:12:30PM -0600, Anthony Liguori wrote:
Artyom Tarasenko wrote:
I thought attaching a second copy were the way to send the patch properly.
Attaching as an application/octet-stream is not terribly helpful. It
basically means you've attached a binary blob.
Is the
On Wed, Dec 2, 2009 at 7:56 PM, Alexander Graf ag...@suse.de wrote:
On 02.12.2009, at 19:53, Artyom Tarasenko wrote:
2009/12/2 Anthony Liguori anth...@codemonkey.ws:
Artyom Tarasenko wrote:
2009/12/1 Alexander Graf ag...@suse.de:
Hi,
Could someone with commit rights please stand up to
On 02.12.2009 20:12, Anthony Liguori wrote:
Artyom Tarasenko wrote:
I thought attaching a second copy were the way to send the patch
properly.
Attaching as an application/octet-stream is not terribly helpful. It
basically means you've attached a binary blob.
Is the proper way
Riku Voipio wrote:
git pulls have been working really well for linux-user. I'd like to
continue that for new architectures.
I can provide the patches in the same way as git pull requests.
Works for me.
Regards,
Anthony Liguori
Filip Navara wrote:
If only everything was as easy as it sounds. Unfortunately
git-send-email was for long time unavailable to Windows users and even
now it is barely usable and hard to configure. TortoiseGit once again
doesn't work because of the changed setting on the nongnu.org mail
server...
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it getting committed. For kvm/vnc/block I just CC
On 02.12.2009, at 09:26, Aurelien Jarno wrote:
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of
On Wed, 2 Dec 2009, Aurelien Jarno wrote:
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it
On Wed, Dec 02, 2009 at 09:37:16AM +0100, Alexander Graf wrote:
On 02.12.2009, at 09:26, Aurelien Jarno wrote:
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I
On 02.12.2009, at 09:46, Aurelien Jarno wrote:
On Wed, Dec 02, 2009 at 09:37:16AM +0100, Alexander Graf wrote:
On 02.12.2009, at 09:26, Aurelien Jarno wrote:
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel
On 12/02/2009 10:37 AM, Alexander Graf wrote:
On 02.12.2009, at 09:26, Aurelien Jarno wrote:
On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to
2009/12/1 Alexander Graf ag...@suse.de:
Maintainership for a subsystem is completely different from feeling
responsible for patches. You can be the person checking stuff in without
knowing anything about the subsystem. If it breaks, have the community fix
it. If it stays broken and nobody
On Tue, Dec 01, 2009 at 12:51:25PM -0600, Anthony Liguori wrote:
There are some subsystems where nobody feels responsible though,
apparently hoping 'someone else' will tske on it. Well, turns out it
doesn't work that way.
The general problem is that someone has to step up to maintain
On 12/02/2009 01:24 PM, Alexander Graf wrote:
If it leads to removing the subsystem then it's not much gain for the
project and the users :)
I don't know of any succesful project that has maintainers who don't
feel responsible for the code they're comming.
Well the point I was trying
2009/12/1 Alexander Graf ag...@suse.de:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it getting committed. For kvm/vnc/block I just CC
Anthony, for Audio I just CC
Artyom Tarasenko wrote:
2009/12/1 Alexander Graf ag...@suse.de:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it getting committed. For kvm/vnc/block I just CC
2009/12/2 Anthony Liguori anth...@codemonkey.ws:
Artyom Tarasenko wrote:
2009/12/1 Alexander Graf ag...@suse.de:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it
On 02.12.2009, at 19:53, Artyom Tarasenko wrote:
2009/12/2 Anthony Liguori anth...@codemonkey.ws:
Artyom Tarasenko wrote:
2009/12/1 Alexander Graf ag...@suse.de:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to
Artyom Tarasenko wrote:
I thought attaching a second copy were the way to send the patch properly.
Attaching as an application/octet-stream is not terribly helpful. It
basically means you've attached a binary blob.
Is the proper way described somewhere?
The proper way is to use a
Am Mittwoch 02 Dezember 2009 09:54:04 schrieb Alexander Graf:
Experience has shown that it doesn't work like that. It happens the
person writing the patches never provides a fix, and the committer
receives the complains, and in fine fixes the commit.
Then revert the patch. I also think
Hi,
Could someone with commit rights please stand up to feel responsible
for PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it getting committed. For kvm/vnc/block I just CC
Anthony, for Audio I just CC malc, etc.
There are some subsystems
Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible
for PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it getting committed. For kvm/vnc/block I just CC
Anthony, for Audio I just CC malc, etc.
There
On Tue, Dec 1, 2009 at 6:51 PM, Anthony Liguori anth...@codemonkey.ws wrote:
Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for
PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it getting
Blue Swirl wrote:
Of course, my main unclear subsystems are PPC and S390.
I'd recommend the following committers:
PPC: Blue Swirl
S390: Aurelien
If you have other subsystems you feel uncertain on responsibilities,
please add them to the list incl. committer recommendation.
PPC is
On 01.12.2009, at 19:51, Anthony Liguori wrote:
Alexander Graf wrote:
Hi,
Could someone with commit rights please stand up to feel responsible for PPC?
Usually, when I send a patch to qemu-devel, I know who to address to
increase chances of it getting committed. For kvm/vnc/block I
26 matches
Mail list logo
