commit-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[SCM] Hurd branch, master, updated. v0.9.git20230216-70-g3bb1dc4d


From: Samuel Thibault
Subject: [SCM] Hurd branch, master, updated. v0.9.git20230216-70-g3bb1dc4d
Date: Mon, 15 May 2023 12:33:05 -0400 (EDT)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Hurd".

The branch, master has been updated
       via  3bb1dc4d99d3fd17c30a1508f3bbfa3b6b7aac46 (commit)
       via  89d7c97ce5dfca6f54bc1a10577638d94518b0e9 (commit)
       via  0e6a671b828b28b186822f0a2125272781b84c28 (commit)
      from  c1d219c066a5fbf6a6a4c3139f64954dbf12fd02 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3bb1dc4d99d3fd17c30a1508f3bbfa3b6b7aac46
Author: Sergey Bugaev <bugaevc@gmail.com>
Date:   Mon May 15 10:36:00 2023 +0300

    Cosmetic tweaks
    
    Message-Id: <20230515073600.1350072-4-bugaevc@gmail.com>

commit 89d7c97ce5dfca6f54bc1a10577638d94518b0e9
Author: Sergey Bugaev <bugaevc@gmail.com>
Date:   Mon May 15 10:35:59 2023 +0300

    proc: Don't buffer Mach console output
    
    Normally glibc does not buffer tty output, but a devstream backed by
    the Mach console device cannot be isatty'ed. So we need to ask glibc
    explicitly to not buffer it. This is what the startup and mach-defpager
    do already.
    Message-Id: <20230515073600.1350072-3-bugaevc@gmail.com>

commit 0e6a671b828b28b186822f0a2125272781b84c28
Author: Sergey Bugaev <bugaevc@gmail.com>
Date:   Mon May 15 10:35:57 2023 +0300

    exec: Allow loading x86_64 executables on x86_64
    
    Since we don't support mixing i386 and x86_64 binaries on the same
    system (as running them requires different build-time gnumach
    configurations), the exec server can simply require the binary being
    loaded to have been built for the same architecture as the exec server
    itself.
    Message-Id: <20230515073600.1350072-1-bugaevc@gmail.com>

-----------------------------------------------------------------------

Summary of changes:
 exec/exec.c     | 8 +++++++-
 exec/hostarch.c | 9 +++++++++
 proc/main.c     | 1 +
 proc/msg.c      | 4 ++--
 4 files changed, 19 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
Hurd



reply via email to

[Prev in Thread] Current Thread [Next in Thread]