Hi!
On Mon, 26 Oct 2015 20:57:25 +0100, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Quoting Justus Winter (2015-10-05 16:39:46)
> > as agreed earlier, we're trying to produce two releases a year. We
> > released GNU Mach 1.5, GNU MIG 1.5, and GNU Hurd 0.6 in April, hence
> > it is
Hello,
Quoting Justus Winter (2015-10-05 16:39:46)
> as agreed earlier, we're trying to produce two releases a year. We
> released GNU Mach 1.5, GNU MIG 1.5, and GNU Hurd 0.6 in April, hence
> it is time for our next release :)
>
> I have curated a list of noteworthy changes and populated the NE
David Michael, le Mon 12 Oct 2015 17:16:47 -0400, a écrit :
> On Thu, Oct 8, 2015 at 6:18 PM, Samuel Thibault
> wrote:
> > David Michael, le Thu 08 Oct 2015 12:55:13 -0400, a écrit :
> >> Static linking libpthread doesn't work without it.
> >
> > Right. Perhaps libpthread shouldn't be defining _
On Thu, Oct 8, 2015 at 6:18 PM, Samuel Thibault wrote:
> David Michael, le Thu 08 Oct 2015 12:55:13 -0400, a écrit :
>> Static linking libpthread doesn't work without it.
>
> Right. Perhaps libpthread shouldn't be defining __libc_getspecific
> actually.
Thanks for applying all those. After cher
David Michael, le Thu 08 Oct 2015 12:55:13 -0400, a écrit :
> Static linking libpthread doesn't work without it.
Right. Perhaps libpthread shouldn't be defining __libc_getspecific
actually.
Samuel
On Wed, Oct 7, 2015 at 8:17 PM, Samuel Thibault wrote:
> David Michael, le Tue 06 Oct 2015 17:49:00 -0400, a écrit :
>> This one avoids problems with a symbol that is also provided by libpthread:
>> https://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/trunk/debian/patches/hurd-i386/tg-libc_ge
Justus Winter <4win...@informatik.uni-hamburg.de> skribis:
> as agreed earlier, we're trying to produce two releases a year. We
> released GNU Mach 1.5, GNU MIG 1.5, and GNU Hurd 0.6 in April, hence
> it is time for our next release :)
Don’t forget libc! :-)
Ludo’.
Hello,
Thanks for the pending patches notices!
David Michael, le Tue 06 Oct 2015 17:49:00 -0400, a écrit :
> This one avoids problems with a symbol that is also provided by libpthread:
> https://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/trunk/debian/patches/hurd-i386/tg-libc_getspecific.d
Justus Winter, le Wed 07 Oct 2015 00:17:13 +0200, a écrit :
> Quoting David Michael (2015-10-06 23:49:00)
> > Finally, a question on a somewhat related note ... maybe for the next
> > release: I haven't looked into it much yet, but I was thinking maybe
> > gnumach's new boot-time clock could be ex
Manolis Ragkousis, le Wed 07 Oct 2015 17:34:39 +0300, a écrit :
> There is also a patch in the debian glibc called
> "unsubmitted-clock_t_centiseconds.diff" that fixes some test failures
> for programs like guile.
>
> Could this patch be included as well, if a new glibc+libpthread
> snapshot is cr
There is also a patch in the debian glibc called
"unsubmitted-clock_t_centiseconds.diff" that fixes some test failures
for programs like guile.
Could this patch be included as well, if a new glibc+libpthread
snapshot is created?
Thanks,
Manolis
Hi,
Quoting David Michael (2015-10-06 23:49:00)
> Finally, a question on a somewhat related note ... maybe for the next
> release: I haven't looked into it much yet, but I was thinking maybe
> gnumach's new boot-time clock could be exported to provide real
> CLOCK_MONOTONIC support for glibc. Ar
Hi,
On Mon, Oct 5, 2015 at 10:39 AM, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> as agreed earlier, we're trying to produce two releases a year. We
> released GNU Mach 1.5, GNU MIG 1.5, and GNU Hurd 0.6 in April, hence
> it is time for our next release :)
If a new glibc+libpthread
Hello,
It'd be good to work out the pending permission issue with fakeroot
before the release (see the "fakeroot-hurd bug or not?" thread).
Samuel
Hello,
as agreed earlier, we're trying to produce two releases a year. We
released GNU Mach 1.5, GNU MIG 1.5, and GNU Hurd 0.6 in April, hence
it is time for our next release :)
I have curated a list of noteworthy changes and populated the NEWS
files with them. Feel free to commit or suggest an
Congratulations guys, awesome work!!
Manolis
Woohoo! Congratulations to everyone involved! :-)
Ludo’.
Hi!
On Thu, 09 Apr 2015 13:11:05 +0200, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Quoting Thomas Schwinge (2015-04-09 09:57:05)
> > On Wed, 08 Apr 2015 00:35:17 +0200, Justus Winter
> > <4win...@informatik.uni-hamburg.de> wrote:
> > > Quoting Thomas Schwinge (2014-09-23 17:09:30
Quoting Thomas Schwinge (2015-04-09 09:57:05)
> Hi!
>
> On Wed, 08 Apr 2015 00:35:17 +0200, Justus Winter
> <4win...@informatik.uni-hamburg.de> wrote:
> > Quoting Thomas Schwinge (2014-09-23 17:09:30)
> > > The (technical) release process is not the problem; that I can do any
> > > time.
> >
> >
Hi!
On Wed, 08 Apr 2015 00:35:17 +0200, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Quoting Thomas Schwinge (2014-09-23 17:09:30)
> > The (technical) release process is not the problem; that I can do any
> > time.
>
> Awesome! Let's make one now.
:-) Will do tomorrow morning.
I
Quoting Thomas Schwinge (2014-09-23 17:09:30)
> The (technical) release process is not the problem; that I can do any
> time.
Awesome! Let's make one now.
Justus
Quoting Samuel Thibault (2015-01-16 12:08:07)
> Justus Winter, le Fri 16 Jan 2015 12:01:26 +0100, a écrit :
> > No it is not.
>
> You mean in Debian?
Yes.
> > I have a new server that implements the startup protocol, and it
> > neither has a fixed PID nor does it speak the startup protocol over
Justus Winter, le Fri 16 Jan 2015 12:01:26 +0100, a écrit :
> No it is not.
You mean in Debian?
> I have a new server that implements the startup protocol, and it
> neither has a fixed PID nor does it speak the startup protocol over
> its message port.
You mean your recent rewrite of startup in
Quoting Samuel Thibault (2015-01-16 11:56:14)
> Justus Winter, le Fri 16 Jan 2015 11:42:23 +0100, a écrit :
> > I have reimplemented the startup server. The new server does not
> > support the startup protocol over its message port. This change has
> > not made it into the glibc. The shutdown is
Justus Winter, le Fri 16 Jan 2015 11:42:23 +0100, a écrit :
> I have reimplemented the startup server. The new server does not
> support the startup protocol over its message port. This change has
> not made it into the glibc. The shutdown isn't working.
AIUI it is working in the Debian libc th
Justus Winter, le Fri 16 Jan 2015 11:42:23 +0100, a écrit :
> Our development process is severely broken. Or noone gives a shit
> anymore. Or both. I really cannot tell.
Possibly part of the former. Definitely not the latter.
Personally, I've been unfortunately stuck with various unexpected is
Hello :)
Quoting Thomas Schwinge (2014-11-22 18:00:06)
> Justus, believe me, I do understand your frustration. Thank you very
> much for being insistent, instead of just going away.
It has been two months, time to escalate the issue again :)
> > The glibc change is trivial. And even if the cha
On Sun, Nov 23, 2014 at 4:01 PM, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Quoting Samuel Thibault (2014-11-23 21:11:05)
>> Hello,
>>
>> David Michael, le Wed 19 Nov 2014 19:39:43 -0500, a écrit :
>> > The only issue was that /etc/hurd/runsystem.hurd didn't get installed.
>> > I ta
Quoting Samuel Thibault (2014-11-23 21:11:05)
> Hello,
>
> David Michael, le Wed 19 Nov 2014 19:39:43 -0500, a écrit :
> > The only issue was that /etc/hurd/runsystem.hurd didn't get installed.
> > I tacked the following onto patch #4 in the series to try it.
>
> Justus, do we need it?
I guess i
Hello,
David Michael, le Wed 19 Nov 2014 19:39:43 -0500, a écrit :
> The only issue was that /etc/hurd/runsystem.hurd didn't get installed.
> I tacked the following onto patch #4 in the series to try it.
Justus, do we need it?
Samuel
Hi!
Justus, believe me, I do understand your frustration. Thank you very
much for being insistent, instead of just going away.
On Thu, 20 Nov 2014 14:03:43 +0100, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Either more people have to review the patches, or we need to
> change the
Quoting Samuel Thibault (2014-11-20 00:59:23)
> I'm however wondering: I don't see much reviewing being done apart
> from mine. It would help if some people could spend time on reviewing
> patches. I'm not saying taking responsibility for the commit step or
> anything, but just proofreading the s
On Wed, Nov 19, 2014 at 6:59 PM, Samuel Thibault
wrote:
> Justus Winter, le Mon 17 Nov 2014 16:30:18 +0100, a écrit :
>> It has now been 2.5 months since I posted that startup patch series,
>> and 2 months since I suggested rolling new releases.
>>
>> I'm annoye
Justus Winter, le Mon 17 Nov 2014 16:30:18 +0100, a écrit :
> It has now been 2.5 months since I posted that startup patch series,
> and 2 months since I suggested rolling new releases.
>
> I'm annoyed.
I understand this feeling. I'm still waiting (since several years)
fo
hanged is the pid.
> I'm sure Roland is okay with updating the 1 to a 2.
It has now been 2.5 months since I posted that startup patch series,
and 2 months since I suggested rolling new releases.
I'm annoyed.
Justus
Hello :)
Quoting Samuel Thibault (2014-10-06 11:30:26)
> Thomas Schwinge, le Mon 06 Oct 2014 11:22:50 +0200, a écrit :
> > So, anything specific that we should wait for before bundling the next
> > release snapshots?
>
> It'd be nice to include the init->startup series after review. (I'm OK
> wit
Thomas Schwinge, le Mon 06 Oct 2014 11:22:50 +0200, a écrit :
> So, anything specific that we should wait for before bundling the next
> release snapshots?
It'd be nice to include the init->startup series after review. (I'm OK
with the principle, we need to review the patch, and get the glibc ack
Hi!
On Tue, 23 Sep 2014 18:42:00 +0200, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> > [new releases]
> I'll propose updates for the NEWS files.
Thanks for these! (It's of course fine to directly include updates to
those files in any commits whose changes are NEWS-file-worthy.)
I would think that an annual release, or a release every 2 years, coupled
with a snapshot every 2 month, would be the best for most people.
On Tue, Sep 23, 2014 at 1:15 PM, Ludovic Courtès wrote:
> Justus Winter <4win...@informatik.uni-hamburg.de> skribis:
>
> > I understand you took care of the
Justus Winter <4win...@informatik.uni-hamburg.de> skribis:
> I understand you took care of the release process last time. Is this
> process documented somewhere? I think that we should make another
> round of releases. In fact, we should make one or two releases each
> year. At the very least
Quoting Richard Braun (2014-09-23 17:23:49)
> On Tue, Sep 23, 2014 at 05:09:30PM +0200, Thomas Schwinge wrote:
> > For me, the question rather is, what constitutes the releases that we
> > publish? Some new, exciting features (including considerable bug fixing,
> > code re-writes, re-factoring, an
On Tue, Sep 23, 2014 at 05:09:30PM +0200, Thomas Schwinge wrote:
> For me, the question rather is, what constitutes the releases that we
> publish? Some new, exciting features (including considerable bug fixing,
> code re-writes, re-factoring, and so on), on the one hand, or regular
> time-based r
Hi!
On Tue, 23 Sep 2014 16:19:02 +0200, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> I understand you took care of the release process last time. Is this
> process documented somewhere? I think that we should make another
> round of releases. In fact, we should make one or two re
Hi Thomas, hi Samuel :)
I understand you took care of the release process last time. Is this
process documented somewhere? I think that we should make another
round of releases. In fact, we should make one or two releases each
year. At the very least it brings us quite a bit of attention.
If
44 matches
Mail list logo
