> > Does this mean the bug is fixed in 11-current?
> Yes, the bug is fixed in 11-CURRENT, as of Subversion revision r262809.
> > MFC? Is that to 10-STABLE? Your message is less than clear.
> In FreeBSD, fixes are first applied to head (a.k.a -CURRENT), then
> after a certain period they are merged to one more -STABLE branches,
> depending on the type of fix. This procedure is traditionally called
> a Merge From Current, MFC.
> In this particular case, I will merge the fix to both 10-STABLE and
> 9-STABLE. Older branches do not have clang, so merging the fix to
> them makes no sense.
> > I figure if firefox build fails, the bug would affect some other ports as
> > well.
> Don Lewis already mentioned the libxul port, and in general, any port
> based on certain parts of the Mozilla source tree could be affected.
Thanks for response, but I went to FreeBSD website, got to mailing-list
archives, in this case, svn-src-head.
This made me feel safe that the bug was fixed, and I can rebuild 11-head system.
But my last update might have been before the now-squashed bug was introduced.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"