>
> > +FBSD_1.4 {
> > + fdclose;
> > +};
> > +
>
> You also need to update the lib/libc/Versions.def file. Look e.g. at
> the r226217 for the proper way to introduce new version.
>
Updated - thank you.
Cheers,
Mariusz
___
freebsd-current@freebsd.org ma
On Tue, Mar 25, 2014 at 11:25:28PM +0100, Mariusz Zaborski wrote:
> >> [snip]
> >> --- //depot/user/oshogbo/capsicum/lib/libc/stdio/Symbol.map 2013-06-28
> >> 08:51:28.0
> >> +++ /home/oshogbo/p4/capsicum/lib/libc/stdio/Symbol.map 2013-06-28
> >> 08:51:28.0
> >>
On 22 March 2014 08:04, Kevin Oberman wrote:
> On Fri, Mar 21, 2014 at 5:51 PM, Dag-Erling Smørgrav wrote:
>>
>> Warner Losh writes:
>> > It does serve a useful purpose, though, which is why it has endured.
>> > If you were to have a man page that said 'Putc(3) returns ...' then the
>> > automat
> Does this patch allow perl to stop writing to FILE._file? As pointed out
> in
> http://lists.freebsd.org/pipermail/freebsd-current/2013-January/039024.html
> perlio.c in the perl source contains a function
> PerlIOStdio_invalidate_fileno() that should modify a FILE such that
> fclose() does not c
Hello,
I'm using as MUA the famous 'mutt' and from time to time I'm missing a
feature in 'mutt': mark a thread as unwanted to present any new
messages in this thread. This is one I would mark for this.
Thanks
matthias
--
Sent from my FreeBSD netbook
Matthias Apitz, , http://www.unixar
The call to <>
Done. Moving on!
-a
On 22 March 2014 06:40, George Mitchell wrote:
> On 03/21/14 20:51, Dag-Erling Smørgrav wrote:
>>
>> Warner Losh writes:
>>>
>>> It does serve a useful purpose, though, which is why it has endured.
>>> If you were to have a man page that said 'Putc(3)
On 03/21/14 20:51, Dag-Erling Smørgrav wrote:
Warner Losh writes:
It does serve a useful purpose, though, which is why it has endured.
If you were to have a man page that said ‘Putc(3) returns …’ then the
automated tools (and web links) that find Putc.3 wouldn’t be able to since
it doesn’t exis
On Fri, Mar 21, 2014 at 5:51 PM, Dag-Erling Smørgrav wrote:
> Warner Losh writes:
> > It does serve a useful purpose, though, which is why it has endured.
> > If you were to have a man page that said ‘Putc(3) returns …’ then the
> > automated tools (and web links) that find Putc.3 wouldn’t be ab
Warner Losh writes:
> It does serve a useful purpose, though, which is why it has endured.
> If you were to have a man page that said ‘Putc(3) returns …’ then the
> automated tools (and web links) that find Putc.3 wouldn’t be able to since
> it doesn’t exist.
Moreover - if FreeBSD were written in
Ian Lepore writes:
> Just as the age of a moronic "rule" such as this doesn't in any way
> justify the idea that it could never be changed.
I never claimed it did, but I can see how it would be convenient to
pretend that I did so you can attack that instead of discussing the
actual issue.
DES
--
On Mar 21, 2014, at 11:20 AM, Ian Lepore wrote:
> On Fri, 2014-03-21 at 17:54 +0100, Dag-Erling Smørgrav wrote:
>> Warren Block writes:
>>> Dag-Erling Smørgrav writes:
I mean the FreeBSD project, and the reason is as John stated: all
sentences must start with a capital letter. I've
On Fri, 2014-03-21 at 17:54 +0100, Dag-Erling Smørgrav wrote:
> Warren Block writes:
> > Dag-Erling Smørgrav writes:
> > > I mean the FreeBSD project, and the reason is as John stated: all
> > > sentences must start with a capital letter. I've gotten so used to
> > > this over the past 15 years
Warren Block writes:
> Dag-Erling Smørgrav writes:
> > I mean the FreeBSD project, and the reason is as John stated: all
> > sentences must start with a capital letter. I've gotten so used to
> > this over the past 15 years that I even do it in email and other
> > non-FreeBSD written material.
>
On Fri, 21 Mar 2014, Dag-Erling Smørgrav wrote:
Warren Block writes:
Dag-Erling Smørgrav writes:
We always use [The .Nm foo utility or The .Fn foo function] instead
of just .Nm or .Fn at the start of a sentence, but never (or rarely)
within a sentence.
By "we", do you mean the FreeBSD proje
On Mar 21, 2014, at 8:18 AM, Dag-Erling Smørgrav wrote:
> Warren Block writes:
>> Dag-Erling Smørgrav writes:
>>> We always use [The .Nm foo utility or The .Fn foo function] instead
>>> of just .Nm or .Fn at the start of a sentence, but never (or rarely)
>>> within a sentence.
>> By "we", do y
Warren Block writes:
> Dag-Erling Smørgrav writes:
> > We always use [The .Nm foo utility or The .Fn foo function] instead
> > of just .Nm or .Fn at the start of a sentence, but never (or rarely)
> > within a sentence.
> By "we", do you mean the FreeBSD project or your local organization?
> Is th
On Thu, 20 Mar 2014, Dag-Erling Smørgrav wrote:
Warren Block writes:
John Baldwin writes:
Warren Block writes:
.Fn fdclose
is equivalent to
.Fn fclose ,
but the file descriptor is returned rather than closed.
Yes, but this has the 'no capital letter at the start of a sentence'
problem.
I
Warren Block writes:
> John Baldwin writes:
> > Warren Block writes:
> > > .Fn fdclose
> > > is equivalent to
> > > .Fn fclose ,
> > > but the file descriptor is returned rather than closed.
> > Yes, but this has the 'no capital letter at the start of a sentence'
> > problem.
> I've heard that m
On Wednesday, March 19, 2014 4:28:15 pm Warren Block wrote:
> On Wed, 19 Mar 2014, John Baldwin wrote:
>
> > On Wednesday, March 19, 2014 12:38:57 am Warren Block wrote:
> >> On Tue, 18 Mar 2014, John Baldwin wrote:
> >>
> >>> On Monday, March 17, 2014 7:23:19 pm Mariusz Zaborski wrote:
> Hi,
On Tuesday, March 18, 2014 5:35:16 pm Jilles Tjoelker wrote:
> On Tue, Mar 18, 2014 at 12:23:19AM +0100, Mariusz Zaborski wrote:
> > After our previous discuss [1] I prepare fdclosedir(3) function which
> > was committed by Pawel (cc'ed) in commit r254499.
>
> > A while ago I also prepare the fdc
On Wed, 19 Mar 2014, John Baldwin wrote:
On Wednesday, March 19, 2014 12:38:57 am Warren Block wrote:
On Tue, 18 Mar 2014, John Baldwin wrote:
On Monday, March 17, 2014 7:23:19 pm Mariusz Zaborski wrote:
Hi,
After our previous discuss [1] I prepare fdclosedir(3) function which
was committe
On Wednesday, March 19, 2014 12:38:57 am Warren Block wrote:
> On Tue, 18 Mar 2014, John Baldwin wrote:
>
> > On Monday, March 17, 2014 7:23:19 pm Mariusz Zaborski wrote:
> >> Hi,
> >>
> >> After our previous discuss [1] I prepare fdclosedir(3) function which
> >> was committed by Pawel (cc'ed) i
On Tue, 18 Mar 2014, John Baldwin wrote:
On Monday, March 17, 2014 7:23:19 pm Mariusz Zaborski wrote:
Hi,
After our previous discuss [1] I prepare fdclosedir(3) function which
was committed by Pawel (cc'ed) in commit r254499.
A while ago I also prepare the fdclose function. Unfortunately, th
On Tue, 18 Mar 2014, John Baldwin wrote:
On Monday, March 17, 2014 7:23:19 pm Mariusz Zaborski wrote:
...
I think the code is fine. I have a few suggestions on the manpage wording:
.Sh RETURN VALUES
-Upon successful completion 0 is returned.
+The
+.Fn fcloseall
+function return no value.
+.Pp
On Tue, Mar 18, 2014 at 12:23:19AM +0100, Mariusz Zaborski wrote:
> After our previous discuss [1] I prepare fdclosedir(3) function which
> was committed by Pawel (cc'ed) in commit r254499.
> A while ago I also prepare the fdclose function. Unfortunately, this
> new function is a little bit more
On Monday, March 17, 2014 7:23:19 pm Mariusz Zaborski wrote:
> Hi,
>
> After our previous discuss [1] I prepare fdclosedir(3) function which
> was committed by Pawel (cc'ed) in commit r254499.
>
> A while ago I also prepare the fdclose function. Unfortunately, this
> new function is a little bit
26 matches
Mail list logo
