From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGbmk-0000xj-Q9 for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:45:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGbmg-0000sf-3h for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:45:22 -0400 Received: from [199.232.76.173] (port=52934 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGbmf-0000sc-Rk for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:45:17 -0400 Received: from mail-fx0-f209.google.com ([209.85.220.209]:38557) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MGbmf-0004wA-77 for qemu-devel@nongnu.org; Tue, 16 Jun 2009 12:45:17 -0400 Received: by fxm5 with SMTP id 5so1491400fxm.34 for ; Tue, 16 Jun 2009 09:45:16 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4A37C8BF.5010209@opensuse.org> References: <20090615151033.GA26401@kos.to> <4A37C8BF.5010209@opensuse.org> Date: Tue, 16 Jun 2009 19:45:16 +0300 Message-ID: Subject: Re: [Qemu-devel] [PATCH 00/21] Pending linux-user patches From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Martin Mohring Cc: Riku Voipio , qemu-devel@nongnu.org On 6/16/09, Martin Mohring wrote: > Riku Voipio wrote: > > On Sun, Jun 14, 2009 at 06:12:06PM +0300, Blue Swirl wrote: > > > >> On 6/12/09, riku.voipio@iki.fi wrote: > >> > >>> From: Riku Voipio > >>> > >>> All the things in linux-user tree at the moment: > >>> > >>> https://git.maemo.org/projects/qemu/gitweb?p=qemu;a=shortlog;h=refs/heads/linux-user-for-upstream > >>> > >>> Since the maemo git hosting regrettably only provides https > >>> transport, you can download the git tree faster if you already > >>> have a git tree: > >>> > >>> git clone git://git.sv.gnu.org/qemu.git > >>> cd qemu > >>> git remote add maemo https://git.maemo.org/projects/qemu > >>> git fetch maemo > >>> git checkout -b linux-user maemo/linux-user-for-upstream > >>> > >>> This tree is constantly rebased against upstream git HEAD, so avoid basing your > >>> work on this branch. > >>> > > > > > >> Constantly? It's already three days old. :-) > >> > > > > More accurate would be "whenever there is updates in the upstream linux-user/ > > subdir that require rebasing", but that might give some people the impression > > that it is actually rabased quite rarely ;-) > > > > > >> Anyway, I pulled the patches with the intention of possibly committing > >> them. But it looks some of them are not ready yet. > >> > > > > The "From:" fields were not intended as signed-off-by replacements, but rather > > to ensure that the authorship info is not lost. With the current mailer setup > > the email header "From:" on the patches sent to the mailing list shows my address, > > and I don't want to take anyones credit away. > > > > I'll have the look at the compiler warning, I didn't see any warnings on my build > > env(s) before mailing. > > > > Is there any chance to accept the bunch of these changes or any reason > to reject them? I was told by some maintainers that currently there is > no maintainer for user mode anymore. Is this true, and is this the > reason? Or is the user mode support "officially" dropped / running out? After the problems are fixed, I'll commit the fixed ones unless there are objections.