Re: [Qemu-devel] [PATCH 00/21] Pending linux-user patches

[Blue Swirl]

On 6/16/09, Martin Mohring <address@hidden> wrote:
> Riku Voipio wrote:
>  > On Sun, Jun 14, 2009 at 06:12:06PM +0300, Blue Swirl wrote:
>  >
>  >> On 6/12/09, address@hidden <address@hidden> wrote:
>  >>
>  >>> From: Riku Voipio <address@hidden>
>  >>>
>  >>>  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.