Re: News 2010-06

2010-07-08 Thread Arne Babenhauserheide
On Thursday 08 July 2010 16:19:59 Thomas Schwinge wrote: > Enhanced, and published: > It looks nice. Many thanks! - Arne signature.asc Description: This is a digitally signed message part.

Re: Article - GNU HURD: Altered visions and lost promise

2010-07-08 Thread Oz
thanks for the clarification On Thu, Jul 8, 2010 at 10:01 AM, wrote: > Hi, > > On Tue, Jul 06, 2010 at 12:15:13AM -0500, Oz wrote: > >> i see the article says that  Marcus Brinkmann and Neal Walfield are >> the main developers. i dont see anything from them on the bug-hurd >> mailing list are th

Re: Article - GNU HURD: Altered visions and lost promise

2010-07-08 Thread olafBuddenhagen
Hi, On Tue, Jul 06, 2010 at 12:15:13AM -0500, Oz wrote: > i see the article says that Marcus Brinkmann and Neal Walfield are > the main developers. i dont see anything from them on the bug-hurd > mailing list are they still the main or most active developers? They aren't -- and that's part of w

Re: mentor

2010-07-08 Thread olafBuddenhagen
Hi, On Tue, Jul 06, 2010 at 09:17:11PM -0500, Oz wrote: > i want to start helping to hack on the hurd is there a mentor-ship > available. I have been on the mailing list for over i year, can > someone help me get involved? If you feel you need formal mentoring, it's probably best if you speak u

Re: News 2010-06

2010-07-08 Thread Thomas Schwinge
Hello! On Fri, Jul 02, 2010 at 09:23:52PM +0200, Arne Babenhauserheide wrote: > I just wrote the Month of the Hurd for last month. Enhanced, and published: Regards, Thomas signature.asc Description: Digital signature

[bug #29655] linkat() fails because __file_name_lookup_at() problems

2010-07-08 Thread Samuel Thibault
Update of bug #29655 (project hurd): Status:None => Fixed Open/Closed:Open => Closed ___ Reply to this item at:

[bug #29655] linkat() fails because __file_name_lookup_at() problems

2010-07-08 Thread Thomas Schwinge
Follow-up Comment #7, bug #29655 (project hurd): The glibc patch has been committed, so I think we can close this issue? ___ Reply to this item at: ___