Re: TODO list?

From: Christopher Arnold (chris_at_terrabee.net)
Date: 06/30/03

  • Next message: Stijn Hoop: "gethostbyname_r"
    Date: Mon, 30 Jun 2003 15:26:00 +0200 (CEST)
    To: Joachim Strömbergson <watchman@ludd.luth.se>
    
    

    On Sun, 29 Jun 2003, Joachim Strömbergson wrote:

    > >>On Sat, 28 Jun 2003, 14:10-0400, Joseph Holland King wrote:
    > >>>
    > >>>this had a fix to begin with, and has a new fix now:
    > >>>Re: kern/23173: read hangs in linux emulation
    > >>>http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/23173
    > >>
    > >>Assigned to maintainer.
    > >
    > > I'm not the maintainer, but I'll commit the patch in a couple of longish
    > > minutes. An MFC will happen sometime next week. Feel free to ping me
    > > at the end of next week if it hasn't been MFC'd by then.
    >
    > Pretty impressive, just by asking about how to contribute, Joshua Oreman
    > have caused one commit of a fix from a PR and the closing of two other
    > PRs. ;-)
    Isn't it!

    > Would it be productive/meaningful if one were to browse through the PR
    > db, check/verify open PRs with fixes and report back to this list with
    > "looks good" fixes so that they then could be commited in the same way
    > as the three PRs reported by Joseph Holland King?
    I have put some time into looking thru the PR db and there is a LOT of
    stuff that either could be closed or could be fixed right away.

    But i guess whats holding me back is the same thing that is holding others
    back. Whats the correct way to get my hands dirty?

    Is Joachim's idea of reporting back to -hackers correct? (I guess that
    would be -ports for ports related issues?)

    Some of the issues are quite fun. I mean how important is it that a
    BusLogic unit dosn't work under FreeBSD 2.2.6? This is a five year old PR,
    half the lifespan of the FreeBSD project... Couldn´t we close kern/7264?

    If someone offers to be my mentor i would gladly walk thru the db and stir
    up some dust. Any volonteer? I can even formulate my questions so you only
    have to answer YES/NO...

    If there isn't any volonteer i guess i just have to start pestering
    everyone on -hackers...

            /Chris
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"


  • Next message: Stijn Hoop: "gethostbyname_r"

    Relevant Pages

    • cvs-src summary for November 22-29
      ... It is intended to help the FreeBSD community keep up with the fast-paced ... You can get old summaries, and an HTML version of this one, at ... objectors to any commit. ... Important bug fixes ...
      (freebsd-current)
    • cvs-src summary for September 28 - October 4
      ... It is intended to help the FreeBSD community keep up with the fast-paced ... You can get old summaries, and an HTML version of this one, at ... on diverted status -- that is, whether they came from a divert socket ... Dag-Erling Smorgrav made a commit to rm, ...
      (freebsd-current)
    • Re: Fast releases demand binary updates.. (Was: Release schedule for 2006)
      ... > stop talking about core... ... about the FreeBSD project. ... > As for the whole installation thing, you need to talk with re (release ... > they'll commit any budget to it... ...
      (freebsd-stable)
    • cvs-src summary for August 16-23
      ... It is intended to help the FreeBSD community keep up with the fast-paced ... You can get old summaries, and an HTML version of this one, at ... In Julian Elischer 's commit described in `Netgraph made 64-bit ... Important bug fixes ...
      (freebsd-current)
    • HEADS UP: APM users on -current!
      ... I've made a commit that has been reported as breaking APM for some people. ... so could folks please report here if things ... avoid problems with some Pentium 4 cpus and some older PPro/Pentium2 ...
      (freebsd-current)