Re: Unattended issues

Being this the situation (Mach hacking considered a waste of time), Jose's idea of having separate mantainers for GNU Mach and GNU Mig becomes IMHO something that should really be taken seriously into discussion. Maintaining and adding new features are different things. If/When Ser4gi

Re: Unattended issues

El dom, 28-08-2005 a las 13:44 -0700, Thomas Bushnell BSG escribió: > Sergio Lopez <[EMAIL PROTECTED]> writes: > > > On my stress test (continuosly building glibc in a loop), that patch > > keeps the number of ext2fs's threads around 200, which is a pretty sane > > number. No "zalloc's panic" nor

Re: Unattended issues

Sergio Lopez <[EMAIL PROTECTED]> writes: > On my stress test (continuosly building glibc in a loop), that patch > keeps the number of ext2fs's threads around 200, which is a pretty sane > number. No "zalloc's panic" nor any other error were noticed. Perhaps > someone else with a little of spare ti

Re: Unattended issues

On 8/28/05, Jose E. Marchesi <[EMAIL PROTECTED]> wrote: > > This is not a bad thing per se if you guys don't feel like working on > Mach anymore, but it would probably be good to communicate this clearly > to people either way, as some still seem to be interested in hacking on > it

Re: Unattended issues

On 8/28/05, Jose E. Marchesi <[EMAIL PROTECTED]> wrote: > > This is not a bad thing per se if you guys don't feel like working on > Mach anymore, but it would probably be good to communicate this clearly > to people either way, as some still seem to be interested in hacking on > it

Re: Unattended issues

El sáb, 27-08-2005 a las 19:52 -0700, Thomas Bushnell BSG escribió: > Sergio Lopez <[EMAIL PROTECTED]> writes: > > > Oh, ok. Could you please help me to ask _all the things involved_ by > > this... > > Sorry, this is now in realm of just the same generic "tell me > everything!" question. > > As

Re: Unattended issues

You need to ask a fairly specific question. If the question is "can you check this in, please?" then you need to, um, ask the people who are handling checkins. It isn't Roland and me. For HEAD it is Roland, for ams-branch it is anyone with commit access. __

Re: Unattended issues

Sergio's patches cannot be commited until his papers are in order. Hence why the seqno thing has not been commited. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: Unattended issues

Sergio Lopez <[EMAIL PROTECTED]> writes: > Oh, ok. Could you please help me to ask _all the things involved_ by > this... Sorry, this is now in realm of just the same generic "tell me everything!" question. As for Mach, no, I don't have time to answer whatever unasked questions someone might imp

Re: Unattended issues

El sáb, 27-08-2005 a las 19:10 -0700, Thomas Bushnell BSG escribió: > Thomas Schwinge <[EMAIL PROTECTED]> writes: > (...) > So, to sum up, if you have a question about design, ask a question. > Questions are in the interrogative mood, come complete with question > marks, and so forth. > Oh, ok

Re: Unattended issues

Thomas Schwinge <[EMAIL PROTECTED]> writes: > Questions have been asked on this mailing list, for example those whose > headers I just quoted in my previous message. > | http://lists.gnu.org/archive/html/bug-hurd/2005-08/msg00076.html> This is not a question; it is a libc patch. > | http://list

Re: Unattended issues

Michael Banck <[EMAIL PROTECTED]> writes: > Are the Hurd developers interested in any new Mach design > changes/feature additions? Probably not. Mach != Hurd. > Neal and Marcus don't seem to (concentrating > on Hurd/L4 instead), so this leaves Thomas and Roland apparently. > Sergio proposed/

Re: Unattended issues

This is not a bad thing per se if you guys don't feel like working on Mach anymore, but it would probably be good to communicate this clearly to people either way, as some still seem to be interested in hacking on it. Since at least one of the two GNU maintainers for the Hurd (Mar

Re: Unattended issues

You could have asked for a simple super-duper experimental CVS branch, or simply given good reasons to add it to a less experimental branch like ams-branch. If Sergio needs more flexibility in order to espontaneous commit his (and other people) experimental/untested patches, i think t

Re: Unattended issues

On Sat, Aug 27, 2005 at 02:09:13PM -0700, Thomas Bushnell BSG wrote: > Thomas Schwinge <[EMAIL PROTECTED]> writes: > > It's very unfortunate for developers that are not (yet ?) that intimate > > with the Hurd and GNU Mach that there is nearly no one available to be > > asked about e.g. design issue

Re: Unattended issues

Thomas Schwinge <[EMAIL PROTECTED]> writes: > It's very unfortunate for developers that are not (yet ?) that intimate > with the Hurd and GNU Mach that there is nearly no one available to be > asked about e.g. design issues; things that are more tricky than fixing > simple bugs, etc. Please ask,

Re: Unattended issues

On Sat, Aug 27, 2005 at 02:09:52PM -0700, Thomas Bushnell BSG wrote: > Sergio Lopez <[EMAIL PROTECTED]> writes: > > > The problem isn't the patches itself. Don't belive to Alfred, I'm not > > claiming to put any patch into the CVS. I'm just asking some design > > issues, to know what's the proper

Re: Unattended issues

Sergio Lopez <[EMAIL PROTECTED]> writes: > The problem isn't the patches itself. Don't belive to Alfred, I'm not > claiming to put any patch into the CVS. I'm just asking some design > issues, to know what's the proper direction to take so this work can > someday become part of the Hurd. Welp, as

Re: Unattended issues

You could have asked for a simple super-duper experimental CVS branch, or simply given good reasons to add it to a less experimental branch like ams-branch. Instead, you spread lies, just don't want to cooperate, and in the most disgusting way try to blame it on me who offered a helping hand. __

Re: Unattended issues

El sáb, 27-08-2005 a las 19:54 +0200, Marco Gerards escribió: > Sergio Lopez <[EMAIL PROTECTED]> writes: > > > Sorry for bothering you, but is there some kind of "magic word" to > > attract the attention from Hurd's Maintainers? > > You are not bothering anyone. You have done a lot of amazing wo

Re: Unattended issues

The patches are huge, the touch lots of things, they change interfaces, they are untested. Applying them blindly (i.e. ASAP) is a complete mistake. Sergio's copyright assignment status is also vauge. All these issues must be fixed, discussed and _tested_. __

Re: Unattended issues

Sergio Lopez <[EMAIL PROTECTED]> writes: > Sorry for bothering you, but is there some kind of "magic word" to > attract the attention from Hurd's Maintainers? You are not bothering anyone. You have done a lot of amazing work and it would be nice if your patches can be applied ASAP. Perhaps if y

Re: Unattended issues

Unless you or anyone else starts paying someone to `deal with development', you shouldn't expect switft responses. They will come when they come. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: Unattended issues

[ CCed to Marcus, Neal, Roland and Thomas. ] On Tue, Aug 23, 2005 at 03:38:30AM +0200, Sergio Lopez wrote: > This issues (there're many more, but I only took the most recent ones) > are still waiting for attention: > [...] Many more, too. Indeed. It's very unfortunate for developers that are no

Re: Unattended issues

Alfred M. Szmidt wrote: Yes... Most communication about the Hurd nowadays is through ##hurd or #hug @ irc.freenode.net. No discussions of importance take place on IRC. All decision making is done here, on the mailing lists. Anyway, the difference in amount of communication about technic

Re: Unattended issues

Sorry for bothering you, but is there some kind of "magic word" to attract the attention from Hurd's Maintainers? Your patches will get looked at, you must understand that we are doing this in our spare time and sometimes we ave other non-important things to do. Please file them to the trac

Re: Unattended issues

El mié, 24-08-2005 a las 09:16 +0300, Ognyan Kulev escribió: > Sergio Lopez wrote: > > El mar, 23-08-2005 a las 08:49 +0300, Ognyan Kulev escribió: > >> IMHO In our case, it's best bugs and patches to be submitted to Savannah > >> . Savannah

Re: Unattended issues

Yes... Most communication about the Hurd nowadays is through ##hurd or #hug @ irc.freenode.net. No discussions of importance take place on IRC. All decision making is done here, on the mailing lists. ___ Bug-hurd mailing list Bug-hurd@gnu.org ht

Re: Unattended issues

Sergio Lopez wrote: Anyway, the features of Savannah doesn't make sense if there's not a maintainer looking at there regularly (and if they are not looking at here, bug-hurd, I doubt they will be looking at there). It definately makes more sense than unresponsed mails because anyone may easily

Re: Unattended issues

El mié, 24-08-2005 a las 09:16 +0300, Ognyan Kulev escribió: > Sergio Lopez wrote: > > El mar, 23-08-2005 a las 08:49 +0300, Ognyan Kulev escribió: > >> IMHO In our case, it's best bugs and patches to be submitted to Savannah > >> . Savannah may be good or b

Re: Unattended issues

On Wed, Aug 24, 2005 at 09:16:05AM +0300, Ognyan Kulev wrote: > Yes... Most communication about the Hurd nowadays is through ##hurd or > #hug @ irc.freenode.net. This is bug, not a feature, of course. IRC should be used for end-user support, specific hacking or bug tracking and socialising, IM

Re: Unattended issues

Jun Inoue wrote: Allow me to butt in here. Is there an archive of some sort of the discussions that take (took) place in those hurd channels? Yes: http://walfield.org/~deride/ My network's firewalled and I can't connect to IRC. (It seems freenode provides no service that would let me work a

Re: Unattended issues

On Wed, 24 Aug 2005 10:20:54 +0300 Ognyan Kulev <[EMAIL PROTECTED]> wrote: > Jun Inoue wrote: > > Allow me to butt in here. Is there an archive of some sort of the > > discussions that take (took) place in those hurd channels? > > Yes: http://walfield.org/~deride/ Oh, so there was one. Thanks!

Re: Unattended issues

On Wed, 24 Aug 2005 09:16:05 +0300 Ognyan Kulev <[EMAIL PROTECTED]> wrote: > Also, IMHO, having an active and fluid > > mailing list is essential for project's health. > > Yes... Most communication about the Hurd nowadays is through ##hurd or > #hug @ irc.freenode.net. Allow me to butt in her

Re: Unattended issues

Sergio Lopez wrote: El mar, 23-08-2005 a las 08:49 +0300, Ognyan Kulev escribió: IMHO In our case, it's best bugs and patches to be submitted to Savannah . Savannah may be good or bad but it's important to have easily accessible record of Hurd's problems.

Re: Unattended issues

El mar, 23-08-2005 a las 08:49 +0300, Ognyan Kulev escribió: > Sergio Lopez wrote: > > This issues (there're many more, but I only took the most recent ones) > > are still waiting for attention: > > IMHO In our case, it's best bugs and patches to be submitted to Savannah >

Re: Unattended issues

Sergio Lopez wrote: This issues (there're many more, but I only took the most recent ones) are still waiting for attention: IMHO In our case, it's best bugs and patches to be submitted to Savannah . Savannah may be good or bad but it's important to have

Unattended issues

Sorry for bothering you, but is there some kind of "magic word" to attract the attention from Hurd's Maintainers? This issues (there're many more, but I only took the most recent ones) are still waiting for attention: http://lists.gnu.org/archive/html/bug-hurd/2005-08/msg00076.html http://lists.g