Jenkins build is still unstable: FreeBSD_HEAD #480

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 11.0-BETA2 may be delayed

On Fri, Jul 15, 2016 at 12:08:57AM +, Glen Barber wrote: > On Wed, Jul 13, 2016 at 11:10:17PM +, Glen Barber wrote: > > As I am sure you have already seen, there is an issue in 11.0-BETA1 that > > has caused some headaches for people. > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi

Jenkins build is still unstable: FreeBSD_HEAD #479

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Jenkins build is still unstable: FreeBSD_HEAD #478

sorry. -- rollingbits -- rollingb...@gmail.com, rollingb...@terra.com.br rollingb...@yahoo.com, rollingb...@globo.com On Jul 20, 2016 10:32 PM, "rollingbits (Lucas)" wrote: > -- > rollingbits -- rollingb...@gmail.com, rollingb...@terra.com.br > rollingb...@yahoo.com, rollingb...@globo.com > >

Re: Jenkins build is still unstable: FreeBSD_HEAD #478

-- rollingbits -- rollingb...@gmail.com, rollingb...@terra.com.br rollingb...@yahoo.com, rollingb...@globo.com On Jul 20, 2016 9:31 PM, wrote: > See > > ___ > freebsd-current@freebsd.org mailing list

Jenkins build is still unstable: FreeBSD_HEAD #478

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: UTF-8 by default?

I managed to find some time to have a closer look right now, and there isn't a problem with the `read(2)` (meaning it's a false positive). The code could use some cleanup for easier auditability (or maybe not ... "if it ain't broken, don't fix it!"), but it's otherwise not broken --- well, at least

Re: UTF-8 by default?

On 20 July 2016 at 22:23, Don Lewis wrote: > It passes a fixed-length non-NUL terminated buffer (returned by read(2)) > to mbrtowc(). In addition to the lack of termination, the buffer could > also contain a partial character at its beginning or end if the contents > are UTF-8. > > The Coverity I

Re: UTF-8 by default?

On Wed, Jul 20, 2016 at 09:08:41PM +0200, Baptiste Daroussin wrote: > On Wed, Jul 20, 2016 at 08:38:14PM +0200, Joel Dahl wrote: > > On Wed, Jul 20, 2016 at 04:07:41PM +0200, Baptiste Daroussin wrote: > > > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > > > > On 20 Jul 2016, a

Jenkins build is still unstable: FreeBSD_HEAD #477

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: UTF-8 by default?

On 07/20/16 04:36 PM, Herbert J. Skuhra wrote: > Baptiste Daroussin skrev: >> >> On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: >>> On 20 Jul 2016, at 9:13, Tim Čas wrote: >>> So, without further ado: 1) What are the reasons that UTF-8 isn't the default yet? 2) Wo

Re: UTF-8 by default?

On Wed, Jul 20, 2016 at 10:36:13PM +0200, Herbert J. Skuhra wrote: > Baptiste Daroussin skrev: > > > > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > >> On 20 Jul 2016, at 9:13, Tim Čas wrote: > >> > >> > So, without further ado: > >> > 1) What are the reasons that UTF-8 isn

Re: UTF-8 by default?

Baptiste Daroussin skrev: > > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: >> On 20 Jul 2016, at 9:13, Tim Čas wrote: >> >> > So, without further ado: >> > 1) What are the reasons that UTF-8 isn't the default yet? >> > 2) Would it be possible to make this the default in 11.0

Re: UTF-8 by default?

On 20 Jul, Tim Čas wrote: > On 20 July 2016 at 20:33, Don Lewis wrote: >> wc(1) has problems with its multibyte support pointed out by Coverity >> as I recall. > > Not sure how critical that issue is (e.g. byte counts [`-c`], line > counts [`-l`], and such should still work as intended; whether w

Re: UTF-8 by default?

On Wed, Jul 20, 2016 at 09:22:23PM +0200, Tim Čas wrote: > On 20 July 2016 at 20:33, Don Lewis wrote: > > wc(1) has problems with its multibyte support pointed out by Coverity > > as I recall. > > Not sure how critical that issue is (e.g. byte counts [`-c`], line > counts [`-l`], and such should

Re: UTF-8 by default?

On 20 July 2016 at 20:33, Don Lewis wrote: > wc(1) has problems with its multibyte support pointed out by Coverity > as I recall. Not sure how critical that issue is (e.g. byte counts [`-c`], line counts [`-l`], and such should still work as intended; whether word counts work or not depends on wh

Re: UTF-8 by default?

On Wed, Jul 20, 2016 at 08:38:14PM +0200, Joel Dahl wrote: > On Wed, Jul 20, 2016 at 04:07:41PM +0200, Baptiste Daroussin wrote: > > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > > > On 20 Jul 2016, at 9:13, Tim Čas wrote: > > > > > > > So, without further ado: > > > > 1) Wh

Jenkins build is still unstable: FreeBSD_HEAD #476

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: UTF-8 by default?

On Wed, Jul 20, 2016 at 04:07:41PM +0200, Baptiste Daroussin wrote: > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > > On 20 Jul 2016, at 9:13, Tim Čas wrote: > > > > > So, without further ado: > > > 1) What are the reasons that UTF-8 isn't the default yet? > > > 2) Would it

Re: UTF-8 by default?

On 20 Jul, Baptiste Daroussin wrote: > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: >> On 20 Jul 2016, at 9:13, Tim Čas wrote: >> >> > So, without further ado: >> > 1) What are the reasons that UTF-8 isn't the default yet? >> > 2) Would it be possible to make this the default

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On 20 Jul 2016, at 16:46, Warner Losh wrote: > > I've been trying to get the final spec for it. Right now it's a > disorganized series > of patches, some of which have been merge some that haven't. I'll send you a > copy when I can find something better than "here's the code." Thanks. From the

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Wed, Jul 20, 2016 at 3:05 AM, David Chisnall wrote: > On 20 Jul 2016, at 05:48, Warner Losh wrote: >> >> My concern with this is overlay support. Overlay support for "shields" or >> "badges" is going into upstream GPL dtc shortly. The patches have been >> kicking around for a while and are alm

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Wed, Jul 20, 2016 at 9:45 AM, Warner Losh wrote: > On Wed, Jul 20, 2016 at 3:05 AM, David Chisnall wrote: >> On 20 Jul 2016, at 05:48, Warner Losh wrote: >>> >>> My concern with this is overlay support. Overlay support for "shields" or >>> "badges" is going into upstream GPL dtc shortly. The

Jenkins build is still unstable: FreeBSD_HEAD #475

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: UTF-8 by default?

On 20 July 2016 at 16:07, Baptiste Daroussin wrote: > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: >> On 20 Jul 2016, at 9:13, Tim Čas wrote: >> >> > So, without further ado: >> > 1) What are the reasons that UTF-8 isn't the default yet? >> > 2) Would it be possible to make t

Re: UTF-8 by default?

On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > On 20 Jul 2016, at 9:13, Tim Čas wrote: > > > So, without further ado: > > 1) What are the reasons that UTF-8 isn't the default yet? > > 2) Would it be possible to make this the default in 11.0? What about > > 12.0? > > 3) Assumi

Re: UTF-8 by default?

On 20 Jul 2016, at 9:13, Tim Čas wrote: So, without further ado: 1) What are the reasons that UTF-8 isn't the default yet? 2) Would it be possible to make this the default in 11.0? What about 12.0? 3) Assuming an effort is started towards making UTF-8 the default, what changes would be require

Jenkins build is still unstable: FreeBSD_HEAD #474

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

UTF-8 by default?

Hello! I've just joined this list, so I apologize if this has been discussed before. Today in #freebsd on FreeNode, I've asked whether there was any particular reason why UTF-8 wasn't the default in FreeBSD yet. What followed was a small discussion regarding this, and it seems that there's a good

Jenkins build is still unstable: FreeBSD_HEAD #473

See ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On 20 Jul 2016, at 05:48, Warner Losh wrote: > > My concern with this is overlay support. Overlay support for "shields" or > "badges" is going into upstream GPL dtc shortly. The patches have been > kicking around for a while and are almost ready to go in. We need this feature > and I'd planned on