On Mon, 2006-09-25 at 18:16 +0400, Ruslan Ermilov wrote: > On Mon, Sep 25, 2006 at 01:02:58PM +0000, Bruce M Simpson wrote: > > bms 2006-09-25 13:02:58 UTC > > > > FreeBSD src repository > > > > Modified files: (Branch: RELENG_6) > > sys/netinet in_var.h ip_output.c > > Log: > > MFC: Account for output IP datagrams on the ifaddr where they will > > be sent from, not the first ifaddr on the ifp. > > > > PR: kern/72936 > > Submitted by: alfred > > Reviewed by: andre > > Approved by: re@ > > > > Revision Changes Path > > 1.53.2.3 +14 -3 src/sys/netinet/in_var.h > > 1.242.2.13 +11 -4 src/sys/netinet/ip_output.c > > > Why are these insta MFCs? > >
Sorry, I'm usually much better at making sure things have been in HEAD
for long enough before approving them. But morning coffee hadn't kicked
in before I started processing email today. :-(
It helps a *little* bit if you folks only send in MFC requests after the
minimal 3-day wait period. Some people do that, which is great. But
others are in the habit of asking for the MFC approval immediately after
the initial commit expecting us to hold on to it and reply later.
Usually we manage to sort them out and do the right thing but that
second approach has a higher risk factor and not just the risk of a
premature approval (i.e. if you expect us to hold on to it we *might*
forget about it by the time it's appropriate for approval and it'll be
lost in the shuffle...).
--
Ken Smith
- From there to here, from here to | [EMAIL PROTECTED]
there, funny things are everywhere. |
- Theodore Geisel |
signature.asc
Description: This is a digitally signed message part
