Date: Wed, 09 Apr 1997 17:51:51 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: "Louis A. Mamakos" <louie@TransSys.COM> Cc: David Nugent <davidn@unique.usn.blaze.net.au>, Chuck Robey <chuckr@Glue.umd.edu>, FreeBSD current <freebsd-current@freefall.freebsd.org> Subject: Re: make world Message-ID: <19321.860633511@time.cdrom.com> In-Reply-To: Your message of "Wed, 09 Apr 1997 12:59:33 EDT." <199704091659.MAA19396@whizzo.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I've had very mixed results getting stuff merged into the tree - the
> Brooktree 848 changes I've done got merged because someone with commit
> privs was also actively involved in the process. The socket-timestamp
> kernel code got in. But after two attempts to get simple changes to
> /usr/sbin/moused in (which would keep my mouse working when doing
> 'make world', sigh) and a one-liner to
> /usr/src/sbin/mount/getmntopts.c to fix a bug introduced recently
> introduced that breaks cfs, I dunno what to think.
This happens sometimes and the best I can recommend to *anyone*
faced with desultory response from -committers is to follow this
track:
1. Submit the bug fix or enhancement with send-pr, waiting
for your acknowledgement and assigned tracking number to
be returned.
2. Wait about a week. If it's committed, go back to step
1 for your next change. If not, go to step 3.
3. Send mail to committers@freebsd.org saying "Hey, is *anyone*
going to commit PR#123456 or at least tell me why it's bogus?
Please? Thanks!"
4. Wait a week. If it's still not committed, send mail to
jkh@freebsd.org saying "HEY, THEY'RE IGNORING ME OVER THERE,
HELP JORDAN!!" and I will step in and try to see that it's
resolved somehow, even if I have to commit it myself.
I hate to see this happen to anyone.
Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19321.860633511>
